Flickering from Hardware Acceleration after upgrading to Firefox 113 and installing Windows Update
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: sdneamtu, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
- Update Firefox to 113 from 112.
- Upgrade Windows 11 to KB5026372.
- Browse as normal. Flickering happens
Actual results:
Browser flickers with Hardware acceleration turned on.
Expected results:
No flickering when browsing with Hardware acceleration turned on.
![]() |
||
Updated•2 years ago
|
Comment 1•2 years ago
•
|
||
The about:support text you provided is helpful, but it would be more useful to have one with hardware acceleration turned on.
I will attempt repro on one of my systems today.
It's very likely this is the same bug as https://bugzilla.mozilla.org/show_bug.cgi?id=1638709 but I want to confirm, and I want to know why the mitigation for that is not working, and why it is now happening on Windows 11 (previously we only saw this on Windows 10, modulo a few rare cases on Windows 11 I have witnessed).
Attached the about:config with hw acceleration turned on. I should have known better ;)
Don't hesitate to ask if I need to provide any other piece of information that isn't in the text dump.
Comment 4•2 years ago
|
||
This may be related to the switch to FLIP_SEQUENTIAL
that was recently introduced in 113, and is already being rolled back in 113.0.1 due to reports of video tearing.
- Do you still experience this with v114 Beta?
- Alternatively, does it go away in 113.0 if you set
gfx.webrender.dcomp-apply-1704954
tofalse
? - Alternatively again, does it go away in 113.0 if you set
gfx.webrender.flip-sequential
tofalse
instead?
I have not yet checked the v114 beta, but here are some steps I took.
Starting state is with hardware acceleration turned on.
-
Setting
gfx.webrender.dcomp-apply-1704954
tofalse
and restarting Firefox got rid of the problem. -
If
gfx.webrender.dcomp-apply-1704954: false
, andgfx.webrender.flip-sequential: true
, it isn't broken -
gfx.webrender.dcomp-apply-1704954: true
, andgfx.webrender.flip-sequential: false
, it isn't broken -
gfx.webrender.flip-sequential: true
, andgfx.webrender.flip-sequential: true
, it is broken.
![]() |
||
Updated•2 years ago
|
Comment 7•2 years ago
|
||
In that case, this should have been resolved by the 113.0.1 update. Feel free to reopen if that's not the case.
I recommend leaving gfx.webrender.dcomp-apply-1704954
set to false
permanently unless you experience the NVIDIA driver issues seen in bug 1638709.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•