Closed Bug 1832444 Opened 1 year ago Closed 1 year ago

Flickering from Hardware Acceleration after upgrading to Firefox 113 and installing Windows Update

Categories

(Core :: Graphics, defect)

Firefox 113
Desktop
Windows 11
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: sdneamtu, Unassigned)

References

Details

Attachments

(2 files)

Attached file firefox-support.txt

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0

Steps to reproduce:

  1. Update Firefox to 113 from 112.
  2. Upgrade Windows 11 to KB5026372.
  3. 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.

Component: Untriaged → Graphics
OS: Unspecified → Windows 11
Product: Firefox → Core
Hardware: Unspecified → Desktop

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).

Flags: needinfo?(ahale)

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.

See Also: → 1638709

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 to false?
  • Alternatively again, does it go away in 113.0 if you set gfx.webrender.flip-sequential to false 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 to false and restarting Firefox got rid of the problem.

  • If gfx.webrender.dcomp-apply-1704954: false, and gfx.webrender.flip-sequential: true, it isn't broken

  • gfx.webrender.dcomp-apply-1704954: true, and gfx.webrender.flip-sequential: false, it isn't broken

  • gfx.webrender.flip-sequential: true, and gfx.webrender.flip-sequential: true, it is broken.

I am not seeing issues on version 114.0b3.

Severity: -- → S3

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.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Flags: needinfo?(ahale)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: