[Webkit-unassigned] [Bug 53659] Web Inspector: Better support for finding "leaked" DOM

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 22 14:24:39 PST 2011


--- Comment #11 from Greg Simon <gregsimon at chromium.org>  2011-02-22 14:24:38 PST ---
Created an attachment (id=83390)
 --> (https://bugs.webkit.org/attachment.cgi?id=83390&action=review)
Example showing how JS can cause native growth that can not currently be measured from web inspector or heap profiler

Here is a simple example that demonstrates how to "leak" DOM -- here the allocation shows up in the native heap, not the JS heap (meaning you can't use any js heap profilers to figure it out). Also, because the nodes are out of the document, web inspector does not report anything amiss either.

What is keeping them alive is a JS binding on the parent of this DOM subtree.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list