Closed Bug 1752753 Opened 3 years ago Closed 1 year ago

Firefox seldom pins GPU to 100% in linux

Categories

(Core :: Graphics, defect, P3)

Firefox 96
x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox96 --- wontfix
firefox97 --- ?
firefox98 --- ?

People

(Reporter: bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf, power)

Attachments

(1 file)

Attached file ff.support.string.json

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0

Steps to reproduce:

  1. OS, Linux emerald 5.16.2-arch1-1 #1 SMP PREEMPT Thu, 20 Jan 2022 16:18:29 +0000 x86_64 GNU/Linux
  2. FF Version, Mozilla Firefox 96.0.3
  3. nvidia 495.46-10

I am simply using firefox. I am not watching a video in any of the tabs, No audio, Nothing that uses webgl or anything like that.

I do have a good number of tabs open but most of them are likely suspended since I didn't switch to them after I started the browser.

The "active" tabs at the time were,

  1. AWS Dashboard
  2. AWS Codepipeline dashboard(with 7-8 stages)
  3. Adguard Home(https://github.com/AdguardTeam/AdGuardHome/) dashboard
  4. Bugzilla
  5. A small issue page on Github

Actual results:

For some time, It works fine but suddenly, The GPU fan ramps up and nvidia-smi reports, that GPU is at 100% usage and consuming ~150W.

Sun Jan 30 23:43:38 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 495.46       Driver Version: 495.46       CUDA Version: 11.5     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:0C:00.0  On |                  N/A |
| 32%   61C    P0   171W / 320W |   1593MiB / 10015MiB |     99%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1034      G   /usr/lib/Xorg                     876MiB |
|    0   N/A  N/A      1135      G   picom                              32MiB |
|    0   N/A  N/A      7314      G   telegram-desktop                    3MiB |
|    0   N/A  N/A     10923      G   ...b/thunderbird/thunderbird       93MiB |
|    0   N/A  N/A     12320      G   ...AAAAAAAAA= --shared-files       27MiB |
|    0   N/A  N/A     15751      G   ...AAAAAAAAA= --shared-files       39MiB |
|    0   N/A  N/A     17790      G   alacritty                          10MiB |
|    0   N/A  N/A     18025      G   alacritty                          10MiB |
|    0   N/A  N/A     18159      G   /usr/lib/firefox/firefox            3MiB |
|    0   N/A  N/A     18216      G   /usr/lib/firefox/firefox          468MiB |
+-----------------------------------------------------------------------------+

It stayed like this until I closed all the AWS tabs, Github tab and the Adguard home tab. After this, It went back to normal. After a few seconds, I reopened all the same tabs, Browsed some stuff on those pages but couldn't replicate it.

Expected results:

It should not be consuming this much GPU when I am not really doing anything at all.

I have had this problem since FF 94 but it happens less frequently than before.

I understand there is not a lot of information to debug this but I didn't see a issue for this problem so I hope it's okay to create this.

In another issue, Someone had suggested using mozregression to trace where a problem was introduced but I haven't been able to do that in that issue and probably won't be able to do that for this issue. Initially when I tried to install mozregression, It blew up libc on my machine, I tried to re use it after some weeks but I had ran into more errors.

This problem usually happens when I have had FF open for a few hours(or even days but the PC is suspended over night) so replicating this in a fresh profile will be difficult.

The only extensions I have installed are,

  1. Bitwarden
  2. uBO
  3. FF Containers
  4. Containers proxy
  5. Metamask
Component: Untriaged → Graphics
Keywords: perf
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64
Blocks: wr-nv-linux
Keywords: power

Thanks for the report!
Please open about:config and

  • reset layers.gpu-process.enabled to its default
  • reset/delete layers.mlgpu.enabled
  • reset layout.frame_rate (layout.frame_rate=0 means rendering any animation with max fps=hundreds fps)
  • reset media.ffmpeg.vaapi.enabled (It would only work when using manually compiled nvidia-vaapi-driver which is highly experimental.)
  • reset media.ffvpx.enabled
  • reset media.gpu-process-decoder

and restart Firefox.

Does this problem still occur afterwards?

Hi, I have reset the settings to the suggest value and I'll report back if this happens again.

Severity: -- → S4
Priority: -- → P3

Hey, I have been running this for 10-11 days now and this has not happened again. Soo, I guess one of these settings was causing problems

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

Closing, see Comment 4

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: