Firefox's task manager shows it using ~150MB for tabs and extensions, Window's show it's actually using >2.4GB.
Categories
(Toolkit :: Performance Monitoring, defect)
Tracking
()
People
(Reporter: metasieben, Unassigned)
Details
Attachments
(1 file)
|
343.50 KB,
application/x-gzip
|
Details |
A user has reported unusual memory usage, please see this thread:
https://www.reddit.com/r/firefox/comments/mthsxn/firefoxs_task_manager_shows_it_using_150mb_for/
They also created an anonymized memory report, attached to this bug.
Maybe someone knowledgeable can look at the memory report and give an assessment.
Moreover, about:performace should probably show values that are more inline
with other reporting methods(Task Manager, Activity Monitor).
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
Those are different kinds of numbers, but I don't know who can explain the difference, so moving back to Firefox:Untriaged.
Comment 3•4 years ago
|
||
Hello! I have managed to reproduce the issue with fx 87.0 on Windows 10. Indeed the numbers from about:performance do not match the ones that are shown in task manager.
I have set a component for this issue in order to get our developers involved. If it's not the right component please feel free to change it to change it to an appropriate one.
Thank you!
Updated•4 years ago
|
Comment 4•4 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 5•4 years ago
|
||
(In reply to matthias koplenig [:metasieben] from comment #0)
A user has reported unusual memory usage, please see this thread:
https://www.reddit.com/r/firefox/comments/mthsxn/firefoxs_task_manager_shows_it_using_150mb_for/They also created an anonymized memory report, attached to this bug.
Thanks for attaching it. Nothing seems unusual in this memory report.
Moreover,
about:performaceshould probably show values that are more inline
with other reporting methods(Task Manager, Activity Monitor).
about:processes gives numbers that match the Task Manager pretty closely. about:performance is known to significantly under-report memory use (iirc it only counts memory used by JS objects and DOM nodes).
I see using about:processes has been suggested in the reddit thread.
I'm closing the bug as I see nothing actionable here.
Description
•