Bug 107675 - [chromium] Web Inspector: reduced heap snapshot
Summary: [chromium] Web Inspector: reduced heap snapshot
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Enhancement
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 107665
  Show dependency treegraph
 
Reported: 2013-01-23 05:16 PST by Paul Lewis
Modified: 2013-04-05 13:01 PDT (History)
10 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Lewis 2013-01-23 05:16:25 PST
Allow a developer to see the heap that pertains to their own code, excluding host objects.
Comment 1 Paul Lewis 2013-01-24 03:43:26 PST
More context:

Right now the heap snapshot contains a huge suite of information, a lot of which doesn't pertain to a developer's code. Ideally speaking if there was some way they could see a reduced heap indicating the memory usage of just their own code at any given time it would make identifying memory-expensive objects and leaks easier.
Comment 2 John McCutchan 2013-02-05 09:30:23 PST
It would great if a heap snapshot could be filtered down to only objects explicitly created by code running on the page.
Comment 3 Yury Semikhatsky 2013-02-06 00:43:52 PST
(In reply to comment #2)
> It would great if a heap snapshot could be filtered down to only objects explicitly created by code running on the page.

We're trying to show only objects reachable from DOM windows by default. If we left only objects created by the user's code then we would get lots of objects with no retainers as e.g. global window object wouldn't be in the heap snapshot and all global variable values would become root objects. Also consider references from DOM node wrappers, they would also disappear.
Comment 4 Timothy Hatcher 2013-04-05 13:01:41 PDT
Chromium and V8 have left the building. Won't fix.