On 03/21/2014 12:06 PM, Bill McCloskey wrote:
The problem with doing measurements is that the per-compartment overhead is very dependent on what's going on in the compartment. I tried to enable the B2G compartment merging stuff in desktop Firefox to get a sense of how much of a change there would be [1]. It's hard to tell if it actually saved anything. It broke a lot of stuff, and I had a hard time getting consistent measurements of memory use at startup since the numbers really fluctuate wildly. My best guess is that explicit went from 90MB currently to 70MB with merging. That's a lot, but keep in mind that a bunch of exceptions are thrown all over the place, and we might just be failing to load some important stuff. Hopefully someone can follow up on this.
There may indeed be a lot of breakage. See https://bugzil.la/980752 about the the reuseGlobal=true situation with the addon-sdk loader Object.freeze()-ing Object.prototype. (Which is bad for idioms like Foo.prototype.toString = function() {}.)
Andrew _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
