Open Bug 1730823 Opened 3 years ago Updated 2 years ago

FF 92 High GPU usage randomly

Categories

(Core :: Graphics, defect)

Firefox 92
defect

Tracking

()

UNCONFIRMED
Performance Impact low

People

(Reporter: beattie.michaelj, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf:resource-use)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0

Steps to reproduce:

Watching videos, dragging tabs with videos playing between windows or opening videos in the background.

It has been happening to me intermittently since 92 that I've been trying to figure out how it exactly it is triggered but no luck yet.

Actual results:

GPU usage shoots to 25% on a 1080ti and it then remains at 25% after closing all tabs once the issue occurs once. It only stops once I close ff or the ff gpu process.

Profiler after it occurs:

https://share.firefox.dev/3C4E6lK - Platform
https://share.firefox.dev/3k2nGUI - Graphics
https://share.firefox.dev/2YEVI9c - Media
https://share.firefox.dev/3hoGX0M - Front-end
https://share.firefox.dev/3ElPVWm - Platform - 36s
https://gist.github.com/Saxayone/f1c3eefe2e29b09f77545041b8c0ed36 - About:support

Expected results:

Once closing everything that was open the GPU should no-longer be stuck at 25%.

Profiler of normal use before bug occurs for reference:
https://share.firefox.dev/3EigjR9 - Platform (nothing open)
https://share.firefox.dev/3zfRRfo - Platform (video playing)

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Graphics
Product: Firefox → Core
Blocks: gfx-triage

Thank you for filing!
Please attach your about:support.

Blocks: wr-perf
No longer blocks: gfx-triage
Severity: -- → S3

Oh, we see it now in your list of links :) Thank you!

I see that the profiles show you are using Software WebRender (without D3D11 compositing). You get SW-WR because layers.acceleration.disabled is to true. Did you disable HW compositing as a test? It shouldn't be using the GPU in any meaningful way. If you still the issue with HW acceleration enabled, can you recollect the traces in that case? Thanks!

Flags: needinfo?(beattie.michaelj)

(In reply to Andrew Osmond [:aosmond] from comment #4)

I see that the profiles show you are using Software WebRender (without D3D11 compositing). You get SW-WR because layers.acceleration.disabled is to true. Did you disable HW compositing as a test? It shouldn't be using the GPU in any meaningful way.

HW acceleration is disabled on this computer when I am using the gpu to render or if I'm gpu mining in off-time.
With HW acceleration enabled, I found that just watching videos uses a minimum of 8% gpu, even just repeatedly showing video controls I can see 60% gpu usage spikes and overall decently large spikes just loading a few pages. This can easily impact the gpu mining efficiency+stability especially.
With it disabled the I normally see around 5~8% watching videos with only spikes at maximum I have seen of ~28% with large loads of ~30+ sites simultaneously.

(In reply to Andrew Osmond [:aosmond] from comment #4)

If you still the issue with HW acceleration enabled, can you recollect the traces in that case? Thanks!

With HW acceleration enabled I was able to partially recreate the issue.
I was able to replicate the static high gpu usage (44% w/ HW accel instead vs 25% w/o) part with videos paused/no user actions happening after the point that the issue was triggered.
However this time, when the tab(s?) that were causing the issue closed the issue stopped instead of persisting until ff close/gpu process close.

https://gist.github.com/Saxayone/e266a3577a70d1e34294e9e7c65af2ed - about:support
https://share.firefox.dev/2XBrR1f - Profiler - not sure which, it soft-crashed the nvidia drivers nearer the end while I opened about:support to get that info.

Flags: needinfo?(beattie.michaelj)
Whiteboard: [qf]

Even if layers.acceleration.disabled is set to true, we might still be using the GPU for WebGL, I think. You could try setting webgl.disabled to true and check if that affects this.

However, it does seem very strange that Firefox would keep using the GPU even after the tabs are closed.

Whiteboard: [qf] → [qf:p3:resource]

(In reply to Markus Stange [:mstange] from comment #6)

Even if layers.acceleration.disabled is set to true, we might still be using the GPU for WebGL, I think. You could try setting webgl.disabled to true and check if that affects this.

However, it does seem very strange that Firefox would keep using the GPU even after the tabs are closed.

Changed the webgl.disabled to true and still had it occur.
I also noticed that within about:processes it shows GPU as having 135~165% cpu usage when it was occurring.

See Also: → 1732986

Found a way to consistently and repeatedly cause the issue for myself.

Opening a youtube video to a background tab with middle mouse then dragging that tab to a new window seems to cause it.

I'm not sure if it's due to dragging while/before the video is starting but it seems to cause the GPU process to run constant even after closing the window with the video.

about:processes changes the GPU process's cpu% from idle/<0.1% to stuck at minimum 40% with all tabs closed but it after initializing the issue.

Performance Impact: --- → P3
Whiteboard: [qf:p3:resource]

Have the same issue. GPU is constantly in 26% with no tabs, after restarts and refresh, no addons, default theme.
System is i3770k, gtx660, two monitors (one is 133hz). Latest drivers and all. Tried the following, no change in behavior.

  • Reinstall, new profile.
  • Refresh FF
  • Restart machine
  • gfx.webrender.compositor off, gfx.webrender.force-angle false, webgl.disable-angle true

No change in behavior. It is like this when launched, before opening any page.

You need to log in before you can comment on or make changes to this bug.