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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 3 04:28:51 PST 2011


Mikhail Naganov <mnaganov at chromium.org> changed:

           What    |Removed                     |Added
                 CC|                            |vitalyr at chromium.org

--- Comment #1 from Mikhail Naganov <mnaganov at chromium.org>  2011-02-03 04:28:51 PST ---
Can you please provide more info about the caching system (or provide me with source code pointers privately): what the caching system does? If a node is either in cache or in page's DOM tree, it should be never collected, right? So apparently there is some scenario for nodes disposal.

For the new heap profiler (see https://bugs.webkit.org/show_bug.cgi?id=50510) I maintain a map of unique object IDs for heap contents that help to track objects lifetime. Will this help you?

Some questions:
 - by 'id of the element' do you mean DOM nodes implementation (C++) object addresses, or what?
 - how can I know that a DOM node is held only from VM -- by verifying that refcount == 1?

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