On 11/01/2013 11:52 AM, David Bruant wrote:
One use case of cross-vat communication is the remote debugger
protocol implemented in Firefox/OS. I haven't taken the time to run
over related bugs and follow its development (and probably won't for
now, because it'd be a lot of work), but it'd be interesting to think
of how a cross-vat protocol would have made its implementation
easier/safer/less error-prone/less leak-prone.
Anyone knows how leaky the remote debugger protocol is now?
Hopefully it isn't leaky at all. The protocol uses an explicit-free
model, with some help: all the actors are arranged in a tree, and
certain actions free entire subtrees at once.
So, it may leak for the same sorts of reasons malloc/free-based code
leaks, but the subtree-freeing rules are meant to reduce the amount of
bookkeeping required to the point that it can be managed.
I have no experimental evidence either way. As a programmer, I have
confidence that the way I expect things to work is probably how they're
working in practice.
_______________________________________________
dev-tech-js-engine-internals mailing list
dev-tech-js-engine-internals@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
