1896061 - overall gfx performance issues with firefox drawing content and media playback

Status: RESOLVED WORKSFORME

(Core :: Audio/Video: Playback, defect, P2)

Description

[support]

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

Steps to reproduce:

ORIGINAL BUG: https://bugzilla.redhat.com/show_bug.cgi?id=2278600
Date: 2024-05-02
CPU: AMD Ryzen 5600
GPU: Nvidia RTX 4060
Driver: RPMFusions Nvidia akmod version.

Watching Netflix on second display.

NOTE: Another person reacted on the Bugzilla Report with the same/similar issues.

I suggest to read the entire Bugzilla Report i linked above.

Actual results:

Original Text:

Since "yestderday", but could be a day earlier, i experience partly dramatic performance issues on firefox.

I have a dual display system, using a RTX4060 with nvidias prop drivers from RPMFusion.

Yesterday i noticed for the first time, that video playback inside firefox ( NetFlix ) was lagging on the video track so badly, that the video frames got stuck for seconds. sound was normal, which is an indication that the network stream was not the issue.

While this happend, i checked the gpu stats with nvtop, and there has only been a 40% usage by a game that runs longside on the other display. So the GPU was not the issue.

After restarting performace was a bit better, but no way near normal rates.

From experience with pinephones, it LOOKED LIKE it was a software that tries to do things without a gpu at all.. raw cpu power.

today: using firefox in a normal way to display websites, I can see a performace loss on pages that usually just appear instantly. it's like chewing gum.

2 days later, i got alerts from my personal assisent, that my load increased and checking it showed FF running at 450% without a good reason.

Expected results:

smooth playback / no cpu usage without a reason

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Stephane Travostino]

To note that in my case the issue is only with the Fedora-packaged version of Firefox. The official Mozilla Flatpak has been exhibiting NONE of this behaviour, and I've adopted it as my daily driver over the past week.

Comment 3

[Alastor Wu [:alwu]]

Would you mind to help us capture a profiled result based on this instruction? Also, could you post your about:support as well? Thanks!

Comment 4

[support]

pls see the Bugzilla report.. it's attached there.

If it happens again, ofcourse i can profile it.

Comment 5

[Alastor Wu [:alwu]]

From about:support in redhat's bugzilla, I saw that hardware decoding was disabled by FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED, martin, do you have any thought about this issue? Thanks!

Comment 6

[Martin Stránský [:stransky] (ni? me)]

(In reply to Alastor Wu [:alwu] from comment #5)

From about:support in redhat's bugzilla, I saw that hardware decoding was disabled by FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED, martin, do you have any thought about this issue? Thanks!

This is NVIDIA proprietary drivers, we don't support VA-API there as it's missing on NVIDIA side. It's possible to use workarounds but it's highly experimental and not supposed to work, see https://fedoraproject.org/wiki/Firefox_Hardware_acceleration#Configure_VA-API_Video_decoding_on_NVIDIA

But I'm sure the FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED is also present on working build, (flatpak?), especially as we don't use HW acceleration for DRM content (NetFlix).

Anyway, please test stock Mozilla binaries (not flatpak) directly from Mozilla with clean profile:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries

and report if you see the issues here too.
Thanks.

Comment 7

[support]

setting nvidia-drm.modeset=1 changed

"FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED"

to : "FEATURE_HARDWARE_VIDEO_DECODING_NO_LINUX_NVIDIA"

modeset=0 was done, because PLYMOUTH can't open the screen and reverts back to textconsole booting and noone seems to be interested in fixing it :(

Full Supportentry:

HARDWARE_VIDEO_DECODING
default available
user force_enabled Force enabled by pref
env blocklisted Blocklisted by gfxInfo Blockiert; Fehlercode FEATURE_HARDWARE_VIDEO_DECODING_NO_LINUX_NVIDIA

My guess for the root cause:

$ vainfo
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.18.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
vaInitialize failed with error code -1 (unknown libva error),exit

Which does not even tries to load the nvidia vaapi driver that is installed.

so, what is the actual issue here with vaapi ?

Because:

Profiling the DMABUF shows VAAPI works ( attached )

DMABUF
default available
env blocklisted Blocklisted by gfxInfo Aufgrund bekannter Probleme blockiert: Bug 1788573

This is fixed in NVIDIA 545 Drivers, and we have 550 now.

Comment 8

[support]

Attachment: log.txt-child.24103.moz_log

Comment 9

[support]

Attachment: log.txt-main.4458.moz_log

Comment 10

[support]

BTW: i had no new on this topic issues since thge last GSTREAMER updates were installed:

2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: gstreamer1-plugins-good-gtk-1.22.9-1.fc38.x86_64
2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: gstreamer1-plugins-good-qt-1.22.9-1.fc38.x86_64
2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: gstreamer1-plugins-good-qt6-1.22.9-1.fc38.x86_64
2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: gstreamer1-plugins-good-1.22.9-1.fc38.x86_64
2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: gstreamer1-plugins-base-1.22.9-1.fc38.x86_64
2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: python3-gstreamer1-1.22.9-1.fc38.x86_64
2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: gstreamer1-1.22.9-1.fc38.i686
2024-04-28T10:01:32+0200 SUBDEBUG Upgraded: gstreamer1-1.22.9-1.fc38.x86_64

now issues since this got installed:

2024-05-03T00:01:26+0200 SUBDEBUG Upgrade: gstreamer1-plugins-ugly-1:1.22.11-1.fc38.x86_64
2024-05-03T00:01:26+0200 SUBDEBUG Upgrade: gstreamer1-plugins-bad-freeworld-1:1.22.11-1.fc38.x86_64
2024-05-03T00:01:28+0200 SUBDEBUG Upgraded: gstreamer1-plugins-ugly-1:1.22.9-1.fc38.x86_64
2024-05-03T00:01:28+0200 SUBDEBUG Upgraded: gstreamer1-plugins-bad-freeworld-1:1.22.9-1.fc38.x86_64

We may chase ghosts here.

Comment 11

[support]

Attachment: log-videoplayback-firefox.txt

Comment 12

[support]

Attachment: firefox-new-about:support.txt

Comment 13

[Martin Stránský [:stransky] (ni? me)]

According to firefox-new-about:support.txt everything is OK (but you force enabled VA-API on NVIDIA which may lead to any result). But WebRender looks fine so general HW acceleration should work.

According to log-videoplayback-firefox.txt even VA-API playback works. So I don't see any bug here.

Also note that Firefox doesn't use gstreamer at all, we use ffmpeg (bundled and system one).

Comment 14

[support]

Seems to be fixed - in the last 9 months it did not come back.