Bug 107675
| Summary: | [chromium] Web Inspector: reduced heap snapshot | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Paul Lewis <aerotwist> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Enhancement | CC: | apavlov, john, keishi, loislo, paulirish, pfeldman, pmuellr, vsevik, web-inspector-bugs, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 107665 | ||
Paul Lewis
Allow a developer to see the heap that pertains to their own code, excluding host objects.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Paul Lewis
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.
John McCutchan
It would great if a heap snapshot could be filtered down to only objects explicitly created by code running on the page.
Yury Semikhatsky
(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.
Timothy Hatcher
Chromium and V8 have left the building. Won't fix.