|Summary:||Memory leak due to circular reference Document->DOMTimer->ScheduledAction->[JS objects]->Document|
|Product:||WebKit||Reporter:||Dmitry Titov <dimich>|
|Version:||528+ (Nightly build)|
Description Dmitry Titov 2008-12-06 04:54:36 PST
DOMTimer::stop() will stop the timer but not release the ScheduledAction which holds to a JSFunction which can hold onto a bunch of JS wrappers They can keep a reference back to Document that owns the DOMTimer. Hence, refcount on a Document never goes to 0. Fix is to delete the ScheduledAction in DOMTimer::stop().
Comment 2 Dmitry Titov 2008-12-06 05:20:28 PST
Created attachment 25814 [details] repro file repro file by email@example.com. Set a breakpoint at DOMTimer::stop and ~DOMTimer. Load the file and then close the window. You should see stop() called, then ~DOMTimer() called when Document is destroyed. Before the fix applied, you see only stop(). After the patch with fix applied, both are invoked.
Comment 3 Alexey Proskuryakov 2008-12-06 07:48:19 PST
Comment on attachment 25813 [details] proposed fix r=me I don't think the added null check in DOMTimer destructor is useful, but it isn't harmful either.
Comment 4 Alexey Proskuryakov 2008-12-06 08:04:41 PST
Committed revision 39066.
Comment 5 Darin Adler 2008-12-07 15:15:07 PST
Can we make a test case for this?
Comment 6 Dmitry Titov 2008-12-07 15:52:38 PST
(In reply to comment #5) > Can we make a test case for this? I think it's doable by adding a method to LayoutTestController (getJSObjectCount() which will do GCController::collect first). This way, it's possible to navigate say iframe to a test page and back and then see the number of objects alive. But perhaps there is a simpler way that I don't see?