1776126 - [VAAPI] AMD RX 6600 Sound cut-off in Firefox 101 whilst watching videos on Fedora 36

Status: RESOLVED INACTIVE

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

Description

[Goldmask]

Attachment: FF101_TroubleshootingInfo.txt

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

Steps to reproduce:

(Thank you !)
Machine is running Fedora 36 Workstation with 5.18 kernel.
Audio output is done through my GPU - AMD 6600's HDMI.
Intel GPU is disabled from bios.

• Upgrade to Firefox 101 via software centre update
• Go to Youtube/Twitch or any video playing website
• Play a long running video

I do not have many extensions (attached troubleshooting log) nor anything changed in about:config as I did a fresh FF 101 install.

Actual results:

Sound cuts-off for 2 - 3 seconds every couple of minutes.
This reproduces even if I mute the audio (from tab or from player) and open Cider (audio app on Fedora) and play music from there. Cider's music is always cut-off whenever FF does it.

This does NOT reproduce on Firefox 100 (downloaded .tar and running it locally specifically for Youtube)

Expected results:

Would like to have the sound/audio working properly, without cutting off, as it does in Firefox 100.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

[Paul Adenot (:padenot)]

Reporter, can you please take a "Media" profile with the Firefox Profiler, so that I can look into it?

Video + text instructions here: https://blog.paul.cx/post/profiling-firefox-media-workloads/#the-media-preset, it's trivial to set up (two clicks). Please make sure you're selecting "Media" in the dropdown so that I have the info I need to diagnose this.

Once you've caught the problem in the profiler, you can either send the profile to <[e-mail]> or paste the link or attach here, and I'll have a look. Thanks!

Alternatively, since this is a regression, and you have a clear timeline for it, you can also find the commits that cause this using mozregression. This will download and run Firefox builds, and you can indicate if the build is good or bad, and it will guide you to the range of commits that cause the issue.

The invocation will probably look something like this:

mozregression --good 100 --bad 101

Comment 3

[Goldmask]

(In reply to Paul Adenot (:padenot) from comment #2)

Reporter, can you please take a "Media" profile with the Firefox Profiler, so that I can look into it?

Video + text instructions here: https://blog.paul.cx/post/profiling-firefox-media-workloads/#the-media-preset, it's trivial to set up (two clicks). Please make sure you're selecting "Media" in the dropdown so that I have the info I need to diagnose this.

Once you've caught the problem in the profiler, you can either send the profile to <[e-mail]> or paste the link or attach here, and I'll have a look. Thanks!

Alternatively, since this is a regression, and you have a clear timeline for it, you can also find the commits that cause this using mozregression. This will download and run Firefox builds, and you can indicate if the build is good or bad, and it will guide you to the range of commits that cause the issue.

The invocation will probably look something like this:

mozregression --good 100 --bad 101

Good day Paul - thank you for the fast reply.

Just took a profiler and uploaded it with extensions and source/path. Couldn't publish with all the other checkboxes due to size, but I have it locally and can provide if you need.

Sorry for the huge size - it took a while to replicate. The issue should be at the end of the profiler - I had it reproduce and stopped it after the sound came back.

Here is it: [https://share.firefox.dev/3OhXrpR] (https://share.firefox.dev/3OhXrpR)

Hope it helps - appreciate it!

Comment 4

[Paul Adenot (:padenot)]

Reporter, can you send the full profile by email (<[e-mail]>)? I'm afraid I'm missing something that could be quite important.

Comment 5

[Goldmask]

Done - emailed proton link due to 90mb size. Thanks !

Comment 6

[Paul Adenot (:padenot)]

This profile (received by email) looks unfortunately normal from an audio standpoint. I noticed that this is using VAAPI to decode videos in hardware, using an AMD GPU, presumably the same one that's outputting audio via HDMI.

Do you know if this is something that has started working recently (probably in 101?)? If you take a short profile of the same computer playing the same video on 100, I can tell you that. I'm afraid of a problem in the area.

Comment 7

[Paul Adenot (:padenot)]

Martin, is media.ffmpeg.vaapi.enabled something that Fedora flips to true downstream? It's set to false by default, but doesn't appear in the Important modified preferences section in the about:support attached here.

Comment 8

[Goldmask]

Thank you Paul - I tried setting vaapi to enabled and reproduce a while back, got same outcome.

I'll take another profiler set but problem is I cannot use the exact video as it was a live stream and completely forgot the sections.
Will try to remember or take two profiles of the same video in both versions.

Shall maintain the NMI flag until I return with these. Thanks !

Comment 9

[Goldmask]

Replied via email with Proton link containing 100 and 101 zipped Media profiles using the same video.
101 failed in about 1 minute, stopped it. The other one went without issues and stopped it at 2 minute mark to keep the size small.

Both have the same extensions - Startpage, BetterTTV and of course Profiler (besides the default ones installed by FF).

Forgot to FYI - link expires on the 4th of July, but I can generate another if needed.

Thank you !

Comment 10

[Goldmask]

Quick background information that might be totally useless (why I did not mention it before).
I had my machine running Fedora 36 beta using Intel GPU. Got the AMD that I'm using now and installed that, disabling Intel's GPU.
This was way before F36 release, 5.18 or Firefox 101.

If any of you think it might be relevant, even though FF was freshly installed (to check if repro), I can completely reinstall the system as all my data is on separate drives.

Comment 11

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

(In reply to Paul Adenot (:padenot) from comment #7)

Martin, is media.ffmpeg.vaapi.enabled something that Fedora flips to true downstream? It's set to false by default, but doesn't appear in the Important modified preferences section in the about:support attached here.

about:support prints VAAPI state direcly, see Graphics/Features and VAAPI.

Comment 12

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

Goldmask, can you please set media.hardware-video-decoding.enabled to false at about:config, restart browser and test again? Go to
about:support and look for Graphics/Features section and VAAPI, it should be disabled.
Thanks.

Comment 13

[Goldmask]

(In reply to Martin Stránský [:stransky] (ni? me) from comment #12)

Goldmask, can you please set media.hardware-video-decoding.enabled to false at about:config, restart browser and test again? Go to
about:support and look for Graphics/Features section and VAAPI, it should be disabled.
Thanks.

Thank you Martin - sorry for my delay here !

I set media.hardware-video-decoding.enabled = false and ran the same video as yesterday.
Everything worked properly for the 17 minute runtime of the video. Previously it died in about 1 or 2 minutes.

Could it be something from my hardware configuration? I can keep it to disabled since it doesn't seem to affect video performance/quality.

Comment 14

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

I have the same HW so I can test that.

Comment 15

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

Which audio device do you use? I'm running 4K screen on Display Port and route audio via it and I can't reproduce it.
Audio device is HDMI/DisplayPort2 - Navi 21/23 HDMI/DP Audio Controler.

Comment 16

[Goldmask]

(In reply to Martin Stránský [:stransky] (ni? me) from comment #15)

Which audio device do you use? I'm running 4K screen on Display Port and route audio via it and I can't reproduce it.
Audio device is HDMI/DisplayPort2 - Navi 21/23 HDMI/DP Audio Controler.

HDMI through a Sony 2015 TV, output from it towards a DAC. I didn't touch any of their settings in million of years. No issues with any of my other devices (consoles, windows machine, etc.)

Comment 17

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

If you open Settings/Sound, which audio device is used?

Comment 18

[Goldmask]

HDMI / DisplayPort - Navi 21/23 HDMP/DP Audio Controller
Digital Stereo (HDMI) Output

Comment 19

[Goldmask]

Since you cannot reproduce with the same setup, probably something got mixed on my side after I installed the AMD card.
I can reinstall the system tomorrow, during work hours and try to reproduce without any changes in FF.

What bothers me is why 100 is fine since it has media.hardware-video-decoding.enabled = true (as 101 before I set to false and no repro)

Comment 20

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

Fedora enables VA-API by default in 101.0.1 ahead of upstream. I don't think you need to re-install the system.

Comment 21

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

Any update here? Do you still see that?
Thanks.

Comment 22

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:jimm, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.