Open Bug 1558107 Opened 6 months ago Updated 4 months ago

Occasionally flickering tab title, icons and video length badges (Win10/Intel HD Graphics 4000)


(Core :: Graphics: WebRender, defect, P3)

68 Branch
Windows 10



Tracking Status
firefox68 --- affected
firefox69 --- affected


(Reporter: zdnexnet, Unassigned)


(Blocks 1 open bug)



(7 files)

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

Steps to reproduce:

  1. Activate WebRender on 68 Beta Developer
  2. Go to page and start video
  3. Observe noticeable graphics flickering of controls

Actual results:

You can see Firefox starts to flicker, mostly numbers, window title - page name. Also some other parts, when more inputs are present flickering is more visible.

You can see what happens directly on video.

Expected results:

Page should render without flickering

I have windows 10; Nvidia+Intel graphics; When I deactivate webrender it works correctly.

Component: Untriaged → Graphics: WebRender
Product: Firefox → Core

on 68 Beta Developer

Please reproduce this problem, then open about:support, click on "Copy text to clipboard", paste it into a text file and upload it here (Attach File). Thanks!

OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64

here are data from support page.

Attached file about support.txt
Blocks: wr-intel
See Also: → 1435154, 1556634
Summary: WebRender Windows 10 graphics glithes in interval → YouTube: Occasionally flickering tab title, icons and video length badges (Win10/Intel HD Graphics 4000)

Couldn't repro on Windows machine in the office, should investigate more before shipping on Intel though

Blocks: wr-69
Priority: -- → P3

Okay it seems that this issue happens only sometimes, yesterday it was gone, now it happens all the way. It seems that it is mostly connected with inputs and highlights and window title. Also it seems that in somecases some other inputs are affected. It is every time different.

I am attacching new video.

Btw it is not only youtube. More pages where it happens.

Attached video developer_tools.wmv

Ok, so now I am sure that this is not connected to page. Same thing happens on developer tools. See attached video.

Summary: YouTube: Occasionally flickering tab title, icons and video length badges (Win10/Intel HD Graphics 4000) → Occasionally flickering tab title, icons and video length badges (Win10/Intel HD Graphics 4000)

"adapterDescription": "Intel(R) HD Graphics 4000",
"driverVersion": "",
"driverDate": "4-4-2016",

Does this problem also happen with the latest driver? (from

Well I am not able to install this one as I have Nvidia card also and installer complains about something that manufactured card detected.

But main problem here is that plenty of users have old drivers/cards, how this will be handled?

Also Widows says that this is latest signed driver available (the one which is installed)

Ok, so after using it longer these days it happened several times and I am pretty sure that it is connected more likely to page which has inputs and some active items (developer tools, youtube, pripravto). Usually as i have said it first happens on title and then when user uses input it starts to flicker more and after some time it passes and is usually okay. Weird thing is that it is not always same thing which flickers it changes. On YouTube it is most visible - it starts on search input and then it moves usually on time counters or some active text.

I have another browser - FF67 which is main one and there this does not happen, so I am quite sure it is connected to FF dev with WebRender. Also WebGL works normally I use it quite a lot. Btw I was having also Chrome open and there I did not see these either.

The most important thing here is that I am sure it has to be connected to same redraw of active elements.

So I have updated to newer windows build and it is still same. When I deactivate WebRender it works correctly. I have made new video where you can see what it does now. More panel titles are flashing, sometimes even disappears.

Is here some way how to debug this or get you some more information. It is really not usable.

See Also: → 1562462

The HD 4000 isn't in our initial target audience for Intel so this doesn't need to block 69

No longer blocks: wr-69

Hi, so do you have some news about this? I have tried it on another computer and it is similar result (flickering all around). Funny thing is if you open one FF with this enabled and another without you can almost instantly see difference. Also It seems that WebGL is much slower (actually correct statement should be that whole page is much slower). I accidentally left it open and my colleague in work used it to find stuff and it started to flicker, he suggested that I should use Chrome :D

BTW sometimes is somehow fixed when I start to change panels - usually it works some time. When this happens all flickering and slowness is gone. Do you have some way how to see what is happening? I would like to have this fixed, so I can try to find information.

Btw the newest version of developer 69.0b4 changed the issue to be quite different from start of this bug. Whole page started to flicker and some parts of page have inverted color(black background, white text). I am attaching newest video.

As it seems to help in bug 1556634 you could try this: Open about:config, set gfx.webrender.dcomp-win.enabled to false and restart Firefox. Does it prevent the problem from occuring again?

No it does not help. I have set it. Restarted Firefox and computer and after while it got back. As I have stated now it behaves little differently, instead of just flickering big black which highlights parts of Firefox are displayed. Sometimes after while it disappears and then after time it again starts.

Could you make a screenshot or screencast of that as well?

I have already made it it is in that comment 15. There you can see these big black boxes.

changed issue big black box..

See Also: → 1568799

So I guess this one already confirms what is happening. It would be good if we actually started to work on this. I am able to provide more data or do more tests, would this be possible?

You need to log in before you can comment on or make changes to this bug.