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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=53659





--- Comment #9 from Patrick Mueller <pmuellr at yahoo.com>  2011-02-07 05:26:14 PST ---
(In reply to comment #8)
> Patrik, the problem is what exact kind of API you want?  Plus those low-level APIs sometimes can expose security stuff.  But we can always run a private version of Chromium with some additional stuff exposed and somehow (e.g. C++ defines, or something else) disable it for prod builds.
> 
> But main problem is what kind of API people want and who have enough time and interest to implement them :)

Again, keep in mind this is a meta-comment; it seems like the original problem description is pretty narrow - it's easy to imagine all sorts of "queries" people might want to have like this - to chase down various types of problems.

In terms of an API, the thing I'm most familiar with, publicly, is the Java JVMTI interface:

   http://download.oracle.com/javase/6/docs/platform/jvmti/jvmti.html

here's the API for walking the object space:

   http://download.oracle.com/javase/6/docs/platform/jvmti/jvmti.html#Heap

Yes, YOU can always run a private version of Chrome.  Not many people have that luxury :-)

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