- From: <bugzilla@jessica.w3.org>
- Date: Tue, 02 Apr 2013 19:06:56 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21555 --- Comment #6 from Joshua Bell <jsbell@chromium.org> --- (In reply to comment #4) > One other note: if Chrome is switched to the Gecko behavior, how well would > it handle this: > > store.keyPath.amIGoingToLeak = store; > > ? Gecko handles that via the cycle collector, but I was given to understand > that WebKit doesn't have such a thing.... I believe (but I'm still a n00b here) the way we'd generally handle this is that the persistent keyPath value ends up stashed on the store's JS wrapper object and thus the cycle only occurs in JS and hence is reclaimable; if no references to the wrappers exist they can be reclaimed. But we may have bugs in this area. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 2 April 2013 19:06:58 UTC