GPU task high CPU use (30-40% in about:processes)
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: kiddm_mozilla, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0
Steps to reproduce:
Have not yet been able to isolate.
Actual results:
Sporadically Firefox starts to consume about 10% of a CPU (i.e. about half a core on a quad-core) box when I don't seem to be doing anything, i.e. not say viewing a video in the active tab. When I look under about:processes I see the GPU "process" steadily consuming about 30-50% without any tab specific process showing significant CPU usage. This problem seem to have set in during the Firefox 105 betas (maybe 104).
I'm running Windows 7 with an nVidia NVS 3100M (driver version 21.21.13.4200, driver date: 10/18/2016).
Expected results:
Minimal CPU use
|
Reporter | |
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
|
||
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:gw, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 3•3 years ago
|
||
When this occurs, could you take a profile (see https://profiler.firefox.com/) with the graphics preset and share it here?
|
|
Reporter | |
Comment 4•3 years ago
|
||
So far it has not happened again but if it does I'll take a profile. As it was, I had a lot of tabs open (maybe 50) and was developing a browser add-on so it was a bad time to start knocking out tabs to see if I could isolate the problem to a specific tab.
It would help to know what activities are covered by the GPU pseudo-process and why they can not be assigned to a particular tab.
|
|
Reporter | |
Comment 5•3 years ago
|
||
Well, look at that—the problem resurfaces on Windows 10 using Firefox 105.0.1 with a completely different graphics card (Intel UHD Graphics 630, driver version 27.20.100.9664).
This time I think I can attribute the issue to an interactive feature on the New York Times website, specifically this page:
Today's New York Times home page has an interactive preview of this page. I had to close both the page indicated above and the New York Times home page before CPU use fell to near idle.
Here are two profile captures:
https://share.firefox.dev/3SJNZgQ
https://share.firefox.dev/3BUmhav
Note: This is a big Firefox session (10.6 GB private bytes used by all Firefox processes as shown by the Process Hacker utility) but I have 32 GB of RAM and my total system commit charge is only about 24 GB.
|
|
Reporter | |
Comment 6•3 years ago
|
||
Now I'm seeing it on Windows 7 under Firefox 107.0. Here are two captures with profile settings set to Graphics as recommended in comment 3.
https://share.firefox.dev/3X2aKja
https://share.firefox.dev/3O6SXTO
This time I do not have any tabs open on the New York Times website. The Firefox task manager shows little CPU use for any specific tab, just a nearly constant 50% (half a core) for GPU.
|
||
Updated•1 year ago
|
Description
•