5.3GB of gpu-committed in Firefox Nightly and "Power usage" "Very high" in Task Manager
Categories
(Core :: Graphics, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | affected |
People
(Reporter: alex_mayorga, Unassigned)
Details
(Keywords: 64bit, nightly-community)
Attachments
(2 files)
¡Hola y'all!
Happy 🌮 Thursday!
I have no idea as to why but Firefox Nightly is using over 8.5 GB of RAM and "Power usage" "Very high" in Task Manager.
Can someone take a look into the attached about:memory and suggest how to fix this, por favor?
¡Gracias!
Alex
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Here are some values from the GPU report:
5,330.04 MB ── gpu-committed
2,628.64 MB ── gpu-shared
6,411.25 MB ── private
4,494.89 MB ── resident
4,342.79 MB ── resident-unique
It looks related to graphics.
For the power usage, you'll probably need to attach a report from the Gecko profiler.
Is this a regression?
| Reporter | ||
Comment 2•4 years ago
|
||
¡Hola Andrew!
Thanks for looking into this.
I believe this is a recent regression as I don't recall seeing this high RAM usage and Nightly is my daily driver.
With that said, there's been a recent video driver update too.
In the hopes of helping pin down the issue, I've re-loaded every URL I had opened on 2021-11-04 again today and RAM usage went all the way up to 17 GB.
I captured:
- a graphics profile at https://share.firefox.dev/3BV0JZc
- a platform profile at https://share.firefox.dev/2YqpqiG
- a new about:memory?verbose
Both profiles for about a minute each.
Hope this helps.
Please let me know if you need anything further from the profile or device.
¡Gracias!
Alex
Comment 3•4 years ago
|
||
Thanks for the information. I'm not knowledgeable enough about graphics to do anything further here, but hopefully somebody else who is can take a look.
Comment 4•4 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Alex, are you able to get a GPUview log when the memory is high? There are instructions for how to do that here: https://github.com/servo/webrender/wiki/Debugging-WebRender#anchor_24
You should be able to run log.cmd the second time to stop recording immediately after starting because it will record the necessary information about the memory usage at the beginning.
Please also attach a new about:memory report from the same time that you ran GPUview.
| Reporter | ||
Comment 6•3 years ago
|
||
¡Hola Jeff!
Sorry! I've since lost the list of URLs I had opened on 2021-11-04 so let's resolve this one as incomplete I'd say.
¡Gracias!
Alex
Description
•