On 2014-03-19, 7:58 PM, Kyle Huey wrote:
On Wed, Mar 19, 2014 at 4:52 PM, David Rajchenbach-Teller
<dtel...@mozilla.com> wrote:
Couldn't we insist that any reference to a DOM element in JS (or at
least in JS-implemented components) must be a weak pointer-style
wrapper? I seem to remember that we have introduced something along
these lines a few years ago as a way to fight against leaks of
references to DOM by add-ons.
On 3/20/14 12:39 AM, Kyle Huey wrote:
Followup to dev-platform please.
--
David Rajchenbach-Teller, PhD
Performance Team, Mozilla
The issue is not leaking the DOM elements, it's leaking the (chrome)
JS implementations themselves. Wrapper cutting actually masks these
leaks by stopping them from entraining entire windows past the tests
of these features.
Does it make sense to disable wrapper cutting in (let's say) debug
builds, so that at least we catch some of these badness?
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
