[Affected versions]:
Nightly 75.0a1

[Affected platforms]:
Platforms: Windows

Steps :

1. Open the Firefox Browser and reach https://www.crazygames.com/game/forward-assault
2. Start the game Full Screen.
3. Click the Equipment and then the right arrow to select the next weapon.
4. Click the 28.000 button and click "Play as guest".
5. Click the Create Match button (game mode Team Deathmatch, map Streets) and click the Create Match yellow button.
6. From the Spawn point turn left and go to the first door on the right facing the wall.
7. Keep moving the mouse up and down for a few seconds and move back and forward towards the wall a few times. (might take around 30 seconds untill the glitches start to display)

Expected Results :
There should be no graphical issues displayed.

Actual Results :
White flickers are displayed.

Note: Please note that the this issue only occurs with gfx.webrender.compositor = true
Please also note that I tried to reproduce this issue on a few Desktop PC's with Intel GPU's but without success.
This issue only occurs on a Dell G3 laptop with 2 GPUs but only Intel Activated in about:support

Rares - can you see if you can repro this in Chrome and/or Edge?

I think this is a driver bug - we currently block DirectComposition on Intel HD520 with driver version 24.20.100.6293, which is very close to the driver version being used on this machine according to about:support, which is 24.20.100.6287.

Are you able to update the driver on this machine and check if the bug disappears? If so, we should also add that slightly older driver version to the block list.

This issue does not occur on chrome or edge, aaand now that I've update the driver to 26.20.100.6860 this issue no longer occurs on Firefox either, should we close this with Works for me ? or Invalid ?

Just NI-ing Rares to try downgrading driver again to see if this still reproduces

Please also note that I tried to reproduce this issue on a few Desktop PC's with Intel GPU's but without success.
This issue only occurs on a Dell G3 laptop with 2 GPUs but only Intel Activated in about:support

Rares, can you confirm what driver the machines had where you could not reproduce the issue?

It would also be good to try the driver between 26.20.100.6860 and 24.20.100.6287 to see if it happens there. That will help us figure out what we might need to block and also give Intel info on where the regression might be.

We tried it on an Intel HD 630 with driver v.23.20.16.4973 and the Intel HD 4600 with driver v.20.19.15.4835, as for the Laptop that I was able to reproduce this issue with the old driver version 24.20.100.6287, I was searching through the Intel's catalog for drivers compatible with my GPU and I couldnt find anything in between. Here is the search I used with the subsys ID : https://www.catalog.update.microsoft.com/Search.aspx?q=subsys_086f1028

Maybe Jeff can help me find a working driver between those 2 versions 26.20.100.6860 and 24.20.100.6287 ?

Yeah, I wasn't able to find a driver in between those two either. We should probably follow up with Intel to see if they can tell us what other driver versions are affected.

If you can add a screenshot of what it looks like with the driver rolled back again that would be great

Yep I managed to get a few screenshots of this issue in our latest Nightly build.. it seems now the issue starts to occur the moment the page loads .. you don't have to actually get into the game, and again with Compositor turned off this issue does not occur.

It seems like this issue has gotten a bit worse. Should we block these drivers from getting DC (but not WR)? Is there any debugging we can do to try and see if there is a potential workaround?

I think we should probably block that driver version from DC, although it's worth checking with Jeff to see if that seems reasonable.

I have spent some time investigating it previously, and was unable to find any workaround.

However, if it's likely to affect a large number of devices, it's probably worth spending some more time looking for a workaround. It's probably also worth emailing Intel to see if we can get some information from that about what causes the issue, and what driver version fixes it - that might help us determine if a workaround is feasible.

We are going to not block the driver version for now. It can be fixed by updating the driver.