I should note, I don't think this is possible for JS objects, it certainly would not be possible for arbitrary WebCore/WebKit objects. I noticed the patch was re-landed, which surprises me since we are still discussing it, why was this?
-Sam On Thu, Jun 3, 2010 at 5:02 PM, Timothy Hatcher <timo...@apple.com> wrote: > Even if that wont prevent Sam's proposed information leak, I think this > would be good to do. That way developers only see what they are affecting. > Otherwise a developer might chase a red herring if they have Gmail or > something open in the background and keep seeing spikes of memory are not > caused by their page. > > On Jun 2, 2010, at 2:45 PM, Mikhail Naganov wrote: > > > Used memory count can be restricted to include only objects reachable > > from the caller execution context. In this case, an app could only see > > the amount of memory consumed by itself, not by the whole engine. > > — Timothy Hatcher > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
