Open Bug 1734452 Opened 3 years ago Updated 3 years ago

Flickering Images all over the Firefox Window after duplicated display standby


(Core :: Graphics, defect)

Firefox 92





(Reporter: intet, Unassigned)



(1 file)

5.74 MB, video/quicktime
Attached video IMG_9102.MOV

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

Steps to reproduce:

Connect a second monitor with same resolution and duplicate display output so both show the same. Wait for a while and let computer run while turning off both displays or letting them go to standby. Then turn on one or both displays again.

Details: My displays are one 1440p 240hz Alienware AW2721D and one 60Hz Wacom 27QHD touch. I mine during the night and use one display for gaming one one for working. Whenever I come back to the computer in the morning I have to replug one of my display cables for the issue to be resolved till I walk away for a while. Then it happens again if one display goes to sleep. The Alienware is connected over Displayport and the Wacom over HDMI

Actual results:

Many websites experience bad flickering of all images seemingly randomly all over within the Firefox Window if I hover my mouse over clickable images or links etc. and Youtube are especially bad with the flickering.
Youtube link of a video where it is happening:

Expected results:

Firefox working without flickering of images.,

The Bugbug bot thinks this bug should belong to the 'Core::Layout' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Layout
Product: Firefox → Core

The severity field is not set for this bug.
:TYLin, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(aethanyc)

This looks like a graphics issue.

Component: Layout → Graphics
Flags: needinfo?(aethanyc)

Thanks for the report! Please open about:support, click on "Copy text to clipboard" and paste it here.

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.