Open Bug 1230100 Opened 9 years ago Updated 2 years ago

Black content after display driver crash & recovery

Categories

(Core :: Graphics, defect)

x86_64
Windows 10
defect

Tracking

()

Tracking Status
firefox45 --- affected

People

(Reporter: johnp, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

Windows 10 just reported that my display driver crashed and was successfully recovered. After that I noticed several tabs have black content and new tabs sometimes also are just black. Looks like one of the content processes didn't handle the crash very well, although I'm not even sure if that's even expected.

Windows Event Viewer:
> Event 4101
> Display driver igfx stopped responding and has successfully recovered.

CPU/GPU:i5-4200U with HD Graphics 4400

about:support#graphics:

Graphics
Adapter Description	Intel(R) HD Graphics Family
Adapter Description (GPU #2)	NVIDIA GeForce GT 750M
Adapter Drivers	igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
Adapter Drivers (GPU #2)	nvd3dumx,nvwgf2umx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um
Adapter RAM	Unknown
Adapter RAM (GPU #2)	4095
Asynchronous Pan/Zoom	wheel input enabled
ClearType Parameters	Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50
Device ID	0x0a16
Device ID (GPU #2)	0x0fe4
Direct2D Enabled	true
DirectWrite Enabled	true (10.0.10586.0)
Driver Date	8-4-2015
Driver Date (GPU #2)	10-2-2015
Driver Version	10.18.15.4248
Driver Version (GPU #2)	10.18.13.5850
GPU #2 Active	false
GPU Accelerated Windows	6/6 Direct3D 11 (OMTC)
Subsys ID	079b1025
Subsys ID (GPU #2)	079b1025
Supports Hardware H264 Decoding	Yes
Vendor ID	0x8086
Vendor ID (GPU #2)	0x10de
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
Not sure if this is e10s specific. Milan?
Flags: needinfo?(milan)
Perhaps, but only because of timing.  Any further information would be great - does this happen often, does it happen when gfx.direct2d.disabled is set to true, when it happens, does resizing the window help, does about:support (during the session when bad things happened) contain extra information below "AzureSkiaAccelerated" entry, for example.
Flags: needinfo?(milan)
Whiteboard: [gfx-noted]
I've only seen this display driver crash once, so unfortunately I cannot provide much further information, and as I cannot reproduce the issue, testing with direct2d disabled is not possible. IIRC, I didn't try resizing, but I copied the whole about:support#Graphics section, so there was nothing extra below "AzureSkiaAccelerated".
I'm only working with the device on weekdays, so it may take a couple days to see if I can gather more information.

Just found another bug mentioning the same behaviour: Bug 1128343
Bug 684729 and bug 653055 are also similar, but related to actively switching GPUs in a hybrid graphics setup.
Unfortunately no further luck in trying to reproduce the issue. Dropping the [e10s], as there are other reports showing the same behavior.
Summary: [e10s] Black content after display driver crash & recovery → Black content after display driver crash & recovery

Johannes,
Does this still reproduce when using a current version and similar hardware?

Flags: needinfo?(johnp)
Severity: normal → S3

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(johnp)
You need to log in before you can comment on or make changes to this bug.