7680x2160px/GLX+EGL/Xwayland: Flickering in browser window when scrolling on latest Firefox with AMD GPU (Fixed by Nightly 92 or MOZ_ENABLE_WAYLAND)
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox90 | --- | wontfix |
firefox92 | --- | unaffected |
People
(Reporter: bernhard, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: correctness, regression, regressionwindow-wanted)
Attachments
(1 file)
31.89 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0
Steps to reproduce:
Running latest Firefox on an up to date Arch Linux on Wayland (GNOME).
I've got a dual monitor setup (60hz, 4k) and use an RX580 + the AMD open source GPU driver (extra/mesa 21.1.4-1). After updating to Firefox 90 I'm getting weird flickering in my browser content window when scrolling, and even more frequently when one window is playing a full screen YouTube video.
Steps to reproduce:
- check that gfx.webrender.force-disabled is set to false
- Open a full screen video on one screen
- Open a web page (e.g. reddit) full screen on another screen
- Scroll the reddit web page while playing the video
Actual results:
- Reddit window flickers while scrolling
Expected results:
No flickering. Setting gfx.webrender.force-disabled to true fixes this issue after a browser restart
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Thanks for the report! Please open about:support, click on "copy text to clipboard" and paste it here.
Comment 3•3 years ago
|
||
Thanks!
Background info: Your about:support says "WebRender (Software)", but that's still the default on Xwayland (bug 1696495 comment 8). You might have force-enabled hardware WebRender by setting gfx.webrender.all to true and then force-disabled it again via gfx.webrender.force-disabled=true.
Thoughts:
- Does this bug still occur with https://nightly.mozilla.org?
- Does this still occur if you start Firefox 90 with MOZ_X11_EGL=1 environment variable? (EGL instead of GLX on Xwayland)
- Can this be fixed by starting Firefox 90 with MOZ_ENABLE_WAYLAND=1 environment variable? (Native Wayland backend) Then we could close this as duplicate of bug 1635186.
- Does this still occur if you open about:config in Firefox 90, set gfx.webrender.force-disabled back to false, gfx.webrender.all to true, gfx.webrender.allow-partial-present-buffer-age to false, gfx.webrender.max-partial-present-rects to 0 and restart Firefox? (=Can bug 1677165 be affected by bug 1712969?)
- Please try to find a regression range, if possible:
$ pip3 install mozregression
$ mozregression --good 2021-02-22 --bad 2021-05-31 --pref gfx.webrender.all:true -a https://reddit.com
You can also directly launch dates and try around:
$ mozregression --launch YYYY-MM-DD --pref gfx.webrender.all:true -a https://reddit.com
Thanks for looking into it so quickly. Can confirm that the behavior is not present when running it under native wayland using
MOZ_ENABLE_WAYLAND=1 firefox
Updated•3 years ago
|
Updated•3 years ago
|
Ad 4: these flags in about:config fix the issue for me as well, will try to run the bisect? regression suite but that will probably take a bit of time.
Ad 1) 92.0a1 (2021-07-23) (64-bit) doesn't have this issue
Ad 2) MOZ_X11_EGL=1 flag does not fix it
I don't think I need to run the regression test suite if it seems to be fixed in nightly, correct?
Comment 8•3 years ago
|
||
I think it would still be useful to find the change that actually fixed it, so that we can back-port it to Beta, but it's not critical.
Comment 9•3 years ago
|
||
(In reply to Bernhard from comment #7)
Ad 1) 92.0a1 (2021-07-23) (64-bit) doesn't have this issue
If you have the time, please run this mozregression command to find out what fixed this bug (if it really has been fixed). Thanks!
$ pip3 install mozregression
$ mozregression --find-fix --bad 20210712222033 --good 2021-07-23 --pref gfx.webrender.all:true -a https://www.youtube.com/watch?v=HJp5TKNwiFo -a https://reddit.com
Comment 10•3 years ago
|
||
(Bernhard from comment #7)
Ad 1) 92.0a1 (2021-07-23) (64-bit) doesn't have this issue
Ad 2) MOZ_X11_EGL=1 flag does not fix itI don't think I need to run the regression test suite if it seems to be fixed in nightly, correct?
Updated•3 years ago
|
Description
•