Closed Bug 1524156 Opened 5 years ago Closed 3 years ago

Regression: Video tearing after upgrade to Firefox 65

Categories

(Core :: Graphics, defect, P3)

Product:
Core
Component:
Graphics
Version:
65 Branch
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox-esr60 --- unaffected
firefox65 --- wontfix
firefox66 --- fix-optional
firefox67 --- fix-optional
firefox68 --- wontfix

People

(Reporter: arv, Assigned: stransky)

References

Details

(Keywords: regression)

Attachments

(1 file)

about_support.txt
18.69 KB, text/plain
Details

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

Steps to reproduce:

Upgraded to Firefox 65 on Ubuntu 18.04, from Firefox 64 (64.0+build3-0ubuntu0.18.04.1, 65.0+build2-0ubuntu0.18.04.1). Played video on Netflix and Youtube.

Actual results:

Netflix and Youtube now suffer noticeable video tearing on both partial and full screen video.

Expected results:

Video tearing should not be present, as previously on Firefox 64.

Chrome browser on same system plays video without tearing.

It would be very useful if you could find the regression range.
https://mozilla.github.io/mozregression/quickstart.html

Regardless, please do the following:

  1. Enter about:support in the address bar.
  2. Click the Copy text to clipboard button.
  3. Paste the clipboard contents into a text editor, then save the file.
  4. Click the Attach File link above the description here to upload it.
Has Regression Range: --- → no
status-firefox65: --- → affected
status-firefox-esr60: --- → unaffected
Component: Untriaged → Graphics
Flags: needinfo?(arv)
Keywords: regression
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64
Attached file about_support.txt —

about:support from a new, clean profile (video tearing occurs on this profile when tested)

Flags: needinfo?(arv)

Using Wayland instead of Xorg appears to be a workaround.

I confirm. There was tearing several versions ago (on X11), then it was fixed, and now it is back on version 65. Fullscreen only.

This video helps seeing the problem: https://www.youtube.com/watch?v=0RvIbVmCOxg

System: Ubuntu 18.04 with kernel 4.20.5-042005-generic, AMD GPU (rx 480) with Mesa 18.3.1

Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Martin, is this something you can look in to?

Flags: needinfo?(stransky)

The regression range would be really useful as I'm not aware of any related change in Widget/Gtk. btw. Is it tearing like this one [1]?

Thanks.

[1] https://en.wikipedia.org/wiki/Screen_tearing#/media/File:Tearing_(simulated).jpg

Flags: needinfo?(stransky) → needinfo?(arv)

Unfortunately, I am not in a position to generate a regression range at the moment, sorry.

The tearing is as shown in the image you linked, yes.

Flags: needinfo?(arv)

I gave mozregression-gui a quick go, but unfortunately hit bug #1503358 and am blocked.

(In reply to arv from comment #4)

Using Wayland instead of Xorg appears to be a workaround.

That regression range is critical here as I can't reproduce it.
If mozregression does not work for you, can you try clean FF64 [1]
and for instance 65.0b7 [2] by hand? Just download the tar, unpack it and run as ./firefox. That would be enough for me to find something.

Also I expect you run Ubuntu with Wayland backend enabled, right? Is so, can you try X11 session only without Wayland enabled?

Thanks.

[1] http://archive.mozilla.org/pub/firefox/candidates/64.0-candidates/build3/linux-x86_64/en-US/firefox-64.0.tar.bz2
[2] http://archive.mozilla.org/pub/firefox/candidates/65.0b7-candidates/build1/linux-x86_64/en-US/firefox-65.0b7.tar.bz2

Flags: needinfo?(arv)

Neither of the builds you linked demonstrates the tearing issue. Only my Ubuntu-packaged build does (65.0+build2-0ubuntu0.18.04.1, as noted above).

Flags: needinfo?(arv)

Bingo. Tearing on that one.

Flags: needinfo?(arv)

65.0b10 build1 - no tearing
65.0b11 build1 - no tearing
65.0b12 build1 - tearing

Flags: needinfo?(arv)

That may be https://hg.mozilla.org/releases/mozilla-release/rev/561137bf3210

Can you try to add mozilla.widget.use-argb-visuals key at about:config and test false/true values (you need to restart the browser after the key change) and check the video in FF65? Thanks.

Flags: needinfo?(arv)

Btw. there's the pushlog https://hg.mozilla.org/releases/mozilla-release/pushloghtml/3 and I don't see any video playback related changes between FIREFOX_65_0b12_BUILD1 and FIREFOX_65_0b11_BUILD1 releases.

Adding mozilla.widget.use-argb-visuals and setting it to true seems to get rid of the tearing. Setting to false makes the tearing reoccur.

Flags: needinfo?(arv)

(In reply to arv from comment #18)

Adding mozilla.widget.use-argb-visuals and setting it to true seems to get
rid of the tearing. Setting to false makes the tearing reoccur.

Great, Thanks!

Assignee: nobody → stransky
Blocks: 1516224
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3

I'm having this issue on Elementary OS.

I noticed that when i get this problem the Workspace switch animation stops working, the notifications are overlaped and the minimize shortcut stops working.

I remember that this issue https://bugzilla.mozilla.org/show_bug.cgi?id=1134077 fixed the above problems for me. Now it seems to be back.

(In reply to Blast-City from comment #20)

I'm having this issue on Elementary OS.

I noticed that when i get this problem the Workspace switch animation stops
working, the notifications are overlaped and the minimize shortcut stops
working.

I remember that this issue
https://bugzilla.mozilla.org/show_bug.cgi?id=1134077 fixed the above
problems for me. Now it seems to be back.

Does mozilla.widget.use-argb-visuals help you? If not please file a new bug for that for widget/Gtk+ component and please state Firefox version where you see the regression. Thanks.

Flags: needinfo?(PRESS_1P_START)

btw. I also see Bug 1464679 landed in Firefox 65 which enables compositing with basic layer manager only. Do you use any HW acceleration? (GL/Webredner)?

From about:support, looks like HW acceleration is disabled:

Decision Log
HW_COMPOSITING
blocked by default: Acceleration blocked by platform
OPENGL_COMPOSITING
unavailable by default: Hardware compositing is disabled
WEBRENDER
opt-in by default: WebRender is an opt-in feature
unavailable by runtime: Hardware compositing is disabled
WEBRENDER_QUALIFIED
blocked by env: No qualified hardware

See Also: → 1528292

(In reply to Martin Stránský [:stransky] from comment #21)

(In reply to Blast-City from comment #20)

I'm having this issue on Elementary OS.

I noticed that when i get this problem the Workspace switch animation stops
working, the notifications are overlaped and the minimize shortcut stops
working.

I remember that this issue
https://bugzilla.mozilla.org/show_bug.cgi?id=1134077 fixed the above
problems for me. Now it seems to be back.

Does mozilla.widget.use-argb-visuals help you? If not please file a new bug for that for widget/Gtk+ component and please state Firefox version where you see the regression. Thanks.

Hi.

Adding the mozilla.widget.use-argb-visuals boolean option and setting it to true seems to make the issues reported on my original post stop.

Firefox 65 (Ubuntu repo) with new profile: Tearing on some fullscreen videos.

Firefox 65 (Ubuntu repo) with new profile and mozilla.widget.use-argb-visuals option set to true: No issues.

Flags: needinfo?(PRESS_1P_START)

hi stransky, what's the plan for this bug? (will it be fixed for 68?)

Flags: needinfo?(stransky)

(In reply to Patricia Lawless from comment #25)

hi stransky, what's the plan for this bug? (will it be fixed for 68?)

There's no fix available, it may need some investigation why mozilla.widget.use-argb-visuals fixes that. We can't just set mozilla.widget.use-argb-visuals to true by default as it causes a regression (Bug 1516224).

Flags: needinfo?(stransky)

Bulk change of P3 carryover bugs to wontfix for 68.

status-firefox68: affected → wontfix

Firefox 67.0 on Mint. Small screen-tearing when scrolling through graphics of webpages - e.g. on https://www.bbc.co.uk/news. The problem has been introduced by a recent change of my system - perhaps the update from the previous version of Firefox? Or else just possibly a Linux kernel problem. Adding mozilla.widget.use-argb-visuals boolean as true and restarting the browser does not fix the problem.

OS: Linux Mint 19.1 Tessa x86_64
Host: 20KHCTO1WW ThinkPad X1 Carbon 6th
Kernel: 5.1.5-050105-generic
Resolution: 2560x1440 @ 60.01Hz
DE: Cinnamon 4.0.10
WM: Mutter (Muffin)
CPU: Intel i7-8550U (8) @ 4.000GHz
GPU: Intel UHD Graphics 620
Memory: 2469MiB / 15928MiB
Disk (/dev/nvme0n1p4): 16G / 40G (42%)
Disk (/dev/nvme0n1p2): 222G / 405G (58%)

(In reply to Martin Stránský [:stransky] from comment #16)

That may be https://hg.mozilla.org/releases/mozilla-release/rev/561137bf3210

Can you try to add mozilla.widget.use-argb-visuals key at about:config and test false/true values (you need to restart the browser after the key change) and check the video in FF65? Thanks.

Debian Buster and
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

also has tearing in Fullscreen in Firefox (but also Chrome has it - on Debian Buster) but no tearing in VLC with the same video opened as stream. (So it is a firefox issue - not a general Debian issue)

Video used for test (In VLC and Firefox): https://www.youtube.com/watch?v=0RvIbVmCOxg

The suggestion by Martin Stránský [:stransky] from comment #16 helped to solve the issue. (Tested for about 5 Minutes and no tearing after setting the option to true)

Hi, an interesting experience here.
I'm in Debian 10 64 bits with Gnome 3.30.2 and X11 (not Wayland). 2 PC's, one with a Nvidia 750 Ti and other with Nvidia 1050 Ti. Same driver, officla Nvidia 418 from repositories both.
No problems, but yesterday an update for Firefox 70 to 71. The machine with the 750 begins to tearing in YouTube. Check with Chrome an Opera, no problems.
layers.acceleration.force-enabled setting to true

So today I came here via Google, try the mozilla.widget.use-argb-visuals solution and works with a false value. That 750 machine has an 23 Lg monitor and a Sony TV mirrored.

So I go to the other PC, update FF, try the same solution and don't work. That second PC (the one with the 1050) has two 23 lg monitors, but the second in a vertical position.
No tearing in Yotube in normal size, but in full screen (in the horiozntal monitor, the number 1) is a pain.

I repeat, for years never an issue with Debian 9 and the latest FF versions installed, so now the problem with FF 71 is this.

Thanks for all and sorry for my english.

Some more information: I updated FF in my notebook (Debian 10 64 bits with Gnome 3.30.2, exactly like the other two desktop machines) Dell with an i3 6600U with integrated Intel graphics: tearing in Youtube, mozilla.widget.use-argb-visuals set to false kill the tearing, set to true tearing again.
I hope that this information will be useful, thanks for FF, the best web browser on Earth.

After setting mozilla.widget.use-argb-visuals to true tearing is gone but ghost images are back as mentioned (In reply to Martin Stránský [:stransky] from comment #26)

(In reply to Patricia Lawless from comment #25)

hi stransky, what's the plan for this bug? (will it be fixed for 68?)

There's no fix available, it may need some investigation why mozilla.widget.use-argb-visuals fixes that. We can't just set mozilla.widget.use-argb-visuals to true by default as it causes a regression (Bug 1516224).

If I set layers.acceleration.force-enabled to true the ghost images are gone and no tearing occurs. So both is fixed. Can someone check if there is a regression with the option mentioned by me (layers.acceleration.force-enabled)?

Note: The option layers.acceleration.force-enabled is mentioned in the bug that causes a regression to the option mozilla.widget.use-argb-visuals (Bug 1516224) and in a post on askubuntu: https://askubuntu.com/questions/1102427/strange-ghost-images-transparency-effect-in-full-screen-videos

I'm running the 71.0 release, and I'm noticing tearing, regardless of what I set for layers.acceleration.disabled, or layers.acceleration.force-enabled. It's possible the tearing is less obvious than I noticed before, when layer.acceleration.disabled=true fixed it, on previous releases.

I'm running the 71.0 release, and I'm noticing tearing, regardless of what I set for layers.acceleration.disabled, or layers.acceleration.force-enabled. It's possible the tearing is less obvious than I noticed before, when layer.acceleration.disabled=true fixed it, on previous releases.

Sorry, I spoke too soon. Setting both layers.acceleration.disabled & force-enabled options to false results in significantly worse tearing in youtube video. Setting either to true improves it a lot. There is still minor tearing with either true. There is also tearing on regular pages with smooth scrolling enabled, so it may be related to that.

Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0 -- Arch Linux 5.4.7-arch1-1 -- GNOME 3.34.2 (Xorg - Intel GPU driver)

I'm noticing tearing on full screen (youtube - emby). layers.acceleration.force-enabled didn't help on this release. however it did work on previous releases.

I'm having the same issue as iazami, worked fine on previous releases, works fine in chromium:

Version: 71.0
Build ID: 20191202234414
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
OS: Linux 4.19.91-1-MANJARO

(In reply to iazami from comment #35)

Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0 -- Arch Linux 5.4.7-arch1-1 -- GNOME 3.34.2 (Xorg - Intel GPU driver)

I'm noticing tearing on full screen (youtube - emby). layers.acceleration.force-enabled didn't help on this release. however it did work on previous releases.

(In reply to joewcordingley from comment #36)

I'm having the same issue as iazami, worked fine on previous releases, works fine in chromium:

Version: 71.0
Build ID: 20191202234414
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
OS: Linux 4.19.91-1-MANJARO

okay, this turned out to be an issue with DRI3. possible fixes for Xorg with Intel driver before you decide to report this as a bug:

20-intel.conf (SAN, DRI2)

Section "Device"
   Identifier "Intel Graphics"
   Driver "intel"
   Option "DRI" "2"
   Option "TearFree" "true"
   Option  "TripleBuffer" "true"
EndSection

No DRI, and No Accel (tested on Intel Iris 10th generation):

put MESA_LOADER_DRIVER_OVERRIDE=iris into /etc/environment and then apply the following settings

Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "NoAccel" "True"
  Option "DRI" "False"
EndSection

Here the same issue with amdgpu driver and a amd vega mobility with ryzen 7 3700U.
Webrender enabled is not helping.
Compositing in kwin disabled ( enabling it sometimes help sometimes not)
Plasma 5 desktop in manjaro

Same issue in Gnome 3.38 X11, 81.0.1

What fixed it for me was enabling layers.acceleration.force-enabled and disabling mozilla.widget.use-argb-visuals in about:config. Possible regression, but I'm not too sure.

System info: https://gist.github.com/KingAnde/608f748ba4c8a334213e07c638e028a3

Tested Chrome flatpak and that had no issue out of the box

Taking the freedom to close this as it has become a very mixed bag. If you still see this, please open a new bug with clear steps for reproducing.

By now this should work if using a compositing WM or Wayland. When using a uncomposited WM, tearing is unfortunately expected and the are no plans to change that for the basic backend (software rendering). There's a slight chance that bug 1640779 would fix it for Webrender though.

Context: the latest changes on X11 were bug 1617002 / FF 81, which enabled fullscreen unredirect for some users with composited WMs in compinations with OpenGL/WR. This was fixed in bug 1667116 / FF 83.

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

Attachment

General

Creator:
Created:
Updated:
Size: