Inaccurate memory reporting in about:performance (compared to about:processes, task manager et al.)
Categories
(Toolkit :: Performance Monitoring, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox97 | --- | affected |
People
(Reporter: 1justinpeter, Unassigned)
Details
About:performance does not seem to report memory usage accurately. For example, with this bug form, about:performance, about:processes, and about:memory open, I see the following (total memory across the entire browser; there will be some variation as this wasn't all performed at the exact same time, same set of tabs though):
about:performance: ~75MB
about:processes: ~920MB
about:memory: ~525MB (using "explicit allocations")
Task manager: ~700MB (not all processes are grouped)
Resource monitor:
Commit: ~940MB
Working Set: ~1100MB
Shareable: ~400MB (I assume this isn't a good metric)
Private: ~705MB
About:performance appears to be the clear outlier.
Latest nightly, can provide more information as needed.
|
||
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:florian, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 2•3 years ago
|
||
(In reply to Justin Peter from comment #0)
About:performance does not seem to report memory usage accurately.
about:performance is known to under-report memory. It only reports memory that can definitely be attributed to a specific page (eg. memory used by JS objects created by the page, or DOM nodes of the page) and not memory used by the browser to display the page.
I'm assuming you are on Windows. On Windows about:processes uses the "Working Set - Private" value, which is not perfect, but is the best we can get without causing expensive computations (I explained this a bit in bug 1665318 comment 8).
With Fission being deployed for all users, we will no longer need about:performance and about:processes will replace it.
Description
•