2033161 - [Ubuntu][NVidia] Horizontal Tearing on Video Playback after upgrade to 149.0.2

Status: UNCONFIRMED

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

Description

[itsnotrami]

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

Steps to reproduce:

Ubuntu 24.04.4 LTS
nvidia driver 580.126.09
Geforce 2060Super

Automatic upgrade to 148.0.2 -> 149.0.2 (snap)
switch to apt 149.02 (still has issue)
downgrade back to 148.0.2 on apt issue not present
Downgrading back to 148.0.2 resolves the issue.

Actual results:

Video playback not smooth, horizontal screen tearing.

Expected results:

Video playback e.g. youtube plays smoothly without artifacts, stuttering, or horizontal screen tearing.

Comment 1

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

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

[Karl Tomlinson (:karlt)]

Thank you for the report. Would you be able to use mozregression to bisect to find the change the triggered this, please?
mozregression --good 148 --bad 149 --profile-persistence reuse

Comment 3

[media-triaging-bot]

Thank you for the detailed report and for confirming the regression window (148.0.2 good, 149.0.2 bad).

Karl has already asked for a mozregression bisect — could you please follow up on that? It will pinpoint the exact commit that introduced the regression and help route this to the right team quickly.

While bisecting, could you also provide an about:support report? To get it: open a new tab, type about:support in the address bar, and click "Copy text to clipboard", then paste it here. This will help us understand your graphics configuration (GPU driver, WebRender/compositor status) which is relevant for this type of tearing artifact on NVidia hardware.

Please also capture a media log: follow the instruction video to capture one using about:logging with the "media" preset. After reproducing the issue, save the log file and attach it here. If you have any privacy concerns about sharing the log publicly, please email it to [e-mail] instead.

:stransky, would you mind taking a look when you have a moment? We're seeing a video playback tearing regression on Ubuntu/NVidia that appeared between 148.0.2 and 149.0.2. We'd really appreciate any insight you might have into what could be causing this — do you happen to have any idea?

Comment 4

[itsnotrami]

Yes, I can follow up and run the bisect, might take a couple days to do, my schedule is a little crazy.

Comment 5

[itsnotrami]

Attachment: about_support_capture_last_bad_bisect_step

Comment 6

[itsnotrami]

Attachment: about_support_good_example_from_bisect

Comment 7

[itsnotrami]

I ran the bisect and saved the logs from the command as well as captured all the intermediate about:support dumps and ran about:logging with the media preset for each bad (and one good) step.
I'll attach the last bad step of the bisect here:
Logging link (bad): https://share.firefox.dev/3OPzETI
about:support: (attached)

logging link (good example): https://share.firefox.dev/3OJxZiw
about_support (good example): (attached)

Ping me if you need any more of the info captured.

Comment 8

[itsnotrami]

Oh yeah the bisect results:
1:42.93 INFO: Narrowed integration regression window from [caeb1bb1, 4898d067] (3 builds) to [f9a55c6c, 4898d067] (2 builds) (~1 steps left)
41:42.93 INFO: No more integration revisions, bisection finished.
41:42.93 INFO: Last good revision: f9a55c6cc131183417222cb5d8ef9839c911ca7f
41:42.93 INFO: First bad revision: 4898d067ee28f052f9d1c57ffde37dc0aad68e33
41:42.93 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f9a55c6cc131183417222cb5d8ef9839c911ca7f&tochange=4898d067ee28f052f9d1c57ffde37dc0aad68e33

Comment 9

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

:stransky, since you are the author of the regressor, bug 2001628, could you take a look?

For more information, please visit BugBot documentation.

Comment 10

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

Yes, it's known issue with NVIDIA drivers - needs to be reported there.