Closed
Bug 715178
Opened 13 years ago
Closed 13 years ago
Clicking a title in about:memory doesn't expand or collapse the tree
Categories
(Toolkit :: about:memory, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 719335
Tracking | Status | |
---|---|---|
firefox12 | --- | affected |
People
(Reporter: tonymec, Unassigned)
Details
Mozilla/5.0 (X11; Linux x86_64; rv:12.0a1) Gecko/20120104 Firefox/12.0a1 SeaMonkey/2.9a1 ID:20120104003016
Reproducible: Always
Steps to reproduce:
1. Browse to about:memory
2. (not sure if necessary) Click "More verbose" near the bottom.
3. Click a heading in the tree.
Actual results:
Nothing happens.
Expected results:
According to the bottom line on the page, that branch of the tree should compact (or expand).
Additional info:
Not (yet) tested in Safe Mode.
I'm setting Fx12-affected on the assumption that the about:memory page and everything it uses are common code shared by Firefox and SeaMonkey (there are no status-seamonkey* flags on this Bugzilla page).
The Error Console lists the following:
Warning: reference to undefined property o._hasProblem
Source file: chrome://global/content/aboutMemory.js
Line: 1047
----------
Warning: reference to undefined property aT._kind
Source file: chrome://global/content/aboutMemory.js
Line: 952
----------
Warning: reference to undefined property aT._kind
Source file: chrome://global/content/aboutMemory.js
Line: 551
----------
Warning: anonymous function does not always return a value
Source file: chrome://global/content/aboutMemory.js
Line: 990
----------
Warning: function kindToString does not always return a value
Source file: chrome://global/content/aboutMemory.js
Line: 812
----------
Warning: reference to undefined property o._hasProblem
Source file: chrome://global/content/aboutMemory.js
Line: 1047
----------
Warning: reference to undefined property aT._kind
Source file: chrome://global/content/aboutMemory.js
Line: 952
----------
Warning: reference to undefined property aT._kind
Source file: chrome://global/content/aboutMemory.js
Line: 551
----------
Warning: anonymous function does not always return a value
Source file: chrome://global/content/aboutMemory.js
Line: 990
----------
Warning: function kindToString does not always return a value
Source file: chrome://global/content/aboutMemory.js
Line: 812
Reporter | ||
Comment 1•13 years ago
|
||
Problem persists in Safe Mode, regardless of verbosity.
Comment 2•13 years ago
|
||
wfm in Firefox, fwiw.
Comment 3•13 years ago
|
||
Clicking on "Explicit Allocations" and "Other Measurements" expands and closes for me, nothing else does. I guess that's the expected behavior? tonymec, were you expecting that some of the subtrees like gc-heap might expand or collapse, too?
Comment 4•13 years ago
|
||
> tonymec, were you expecting that some of the subtrees like gc-heap might
> expand or collapse, too?
It could be confusion over the meaning of "heading" in "Click a heading to expand or collapse its tree."
But those warnings in comment 0 don't look right.
Reporter | ||
Comment 5•13 years ago
|
||
(In reply to Nicholas Nethercote [:njn] from comment #4)
> > tonymec, were you expecting that some of the subtrees like gc-heap might
> > expand or collapse, too?
>
> It could be confusion over the meaning of "heading" in "Click a heading to
> expand or collapse its tree."
>
> But those warnings in comment 0 don't look right.
Ah, so it does not *expand* or *collapse* the tree, it only *displays* or *hides* it. For me, "expand or collapse" is like what happens in the left pane of the 3-pane mail window, or in the bookmark window, where each branch at any depth can be expanded or collapsed by clicking the little widget at the root of the branch, toggling it (depending on the current theme) between ▶ and ▼ or between ⊞ and ⊟
So I suppose this bug report is INVALID, unless you want to change the terminology in the bottom line of the page, or fix those error-console warnings.
Comment 6•13 years ago
|
||
Bug 719335 will render this bug moot.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Updated•13 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•