1586040 - [regression] Severely broken on older Intel (gen6) GPU with WR is on

Status: RESOLVED FIXED

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

Description

[YF (Yang)]

Attachment: Screen Recording

See also bug 1585782, it describes some of the process and the machine configuration.

STR:

1. open Firefox, set gfx.webrender.enabled to true in about:config, restart Firefox.
2. open Youtube and play, or feel free to browse some pages.

Actual results:
When I play any YouTube videos (including advertising), playing significant lag, the entire Firefox window often be white, video may sometimes turn green (it appears to be corrupted frames), and after a while Windows say the "Application has been blocked from accessing Graphics." (Recurrent; then Firefox become normal), and even Windows BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL) (rare) on Intel graphics driver.

Attached screen recording to show the problems occurs before the video playback. The problems is more likely to be triggered from YouTube playback.

Expected results:
No lags and white screen, as the old builds.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7793fa575497587b04571a892b899fad9890f43c&tochange=0879b99736d84ff99ebc013fa30dabe1da067b36

p.s. Due to network reasons, the dichotomy has been interrupted, but that should be enough.

Comment 1

[Glenn Watson [:gw]]

Jessie, we'll probably need to find a machine with a Sandy Bridge GT1 (HD 2000) gfx card to be able to debug this.

The oldest Intel GPU I have access to is an HD4600, and I haven't seen any similar issues on that (so far!).

The Windows BSOD suggest a driver bug (it shouldn't be possible to cause this from user code), but perhaps if we can repro it on local hardware we can find a workaround. Unfortunately, it's unlikely that a gfx card that old will receive any driver updates, so a workaround is probably the only possible solution.

Comment 2

[YF (Yang)]

I just found the "Display - Event ID 4101: Display driver igfx stopped responding and has successfully recovered." in Event Viewer - System, after it happened a few times, there are "Application firefox.exe has been blocked from accessing Graphics hardware." (Display - ID 4109) appears.

Comment 3

[Pascal Chevrel:pascalc]

Jessie, Glenn, I see that this bug is marked as not affecting 70 but I also see that it is blocking the Webrender 70 meta bug. Is 70 really not affected? Do we have an estimate on how many users may be affected and if we can find a workaround for 71? Thanks

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Neither 70 nor 71 are affected by this bug. We don't enable WebRender on these cards yet.

Comment 6

[YF (Yang)]

[Tracking Requested - why for this release]:
If the user has enable WR manually, the browser is almost unavailable.

Comment 7

[Pascal Chevrel:pascalc]

Not tracking for 71 as this is not a supported configuration.

Comment 8

[Jeff Muizelaar [:jrmuizel]]

YF (Yang), can you try the latest Nightly and see if it works better for you?

Comment 9

[Jeff Muizelaar [:jrmuizel]]

Actually the fix that I think will help got backed out so it's probably best to wait until it relands.

Comment 10

[YF (Yang)]

This problem is not reproducible after bug 1633628 land.