Closed
Bug 670580
Opened 13 years ago
Closed 12 years ago
Group all compartments together in about:memory
Categories
(Toolkit :: about:memory, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 687724
People
(Reporter: justin.lebar+bug, Unassigned)
Details
There are currently a few reporters directly under js which are easy to miss because they're stuck between the long list of compartments: gc-heap-chunk-unused gc-heap-chunk-admin stack Maybe this would be better if we grouped all the compartments together under js/compartments.
My only concern here is that this will put all of those at the end, pretty much all the time. Maybe that's ok. The current setup is kind of annoying too.
Comment 2•13 years ago
|
||
Grouping them under js/compartments would be the way to do it, I don't want to modify the existing "order sub-trees by size" approach. But I don't think it's necessary. An extra level of indentation for compartments will be annoying. I don't expect the three you name will be significantly easier to find if you don't already know about them.
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to comment #2) > Grouping them under js/compartments would be the way to do it, I don't want > to modify the existing "order sub-trees by size" approach. Agreed. > But I don't think it's necessary. An extra level of indentation for > compartments will be annoying. I don't expect the three you name will be > significantly easier to find if you don't already know about them. It's definitely a tradeoff. I have bigger fish to fry about about:memory, so if you don't think it's worth it, let's not do it. :)
Comment 4•12 years ago
|
||
Bug 702300 is a better way to do this.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Comment 5•12 years ago
|
||
Oh, this is about overlooking the non-compartment entries. Still, per-tab reporting (bug 687724) will render this moot.
You need to log in
before you can comment on or make changes to this bug.
Description
•