Closed
Bug 839079
Opened 13 years ago
Closed 11 years ago
about:tabmemory
Categories
(Toolkit :: about:memory, defect)
Toolkit
about:memory
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mccr8, Unassigned)
Details
(Whiteboard: [MemShrink:P2])
A web developer only cares about memory usage associated with their particular page, and we do a decent job at breaking this down now thanks to CPG, so we should be able to get about:memory-like information for a particular tab, perhaps to be displayed by a developer command line tool.
This is not a pure subset of the existing about:memory information because shared resources like images, strings, etc. probably should be attributed entirely to the tab.
I'm not sure what should be done about heap-unclassified. In some sense it can never be per tab, but on the other hand it does include memory allocated for a particular tab.
|
Reporter | |
Updated•13 years ago
|
Summary: about:memory for a single tab → about:tabmemory
|
|
Reporter | |
Updated•13 years ago
|
Whiteboard: [MemShrink]
|
||
Updated•13 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
|
|
Reporter | |
Comment 1•11 years ago
|
||
We do a decent enough job splitting out memory for a tab in about:memory, I think it is okay to just further improve that.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•