1492871 - Fallback to Basic compositing on a driver update, pdfjs (canvas/webgl?) did not recover properly

Status: RESOLVED WORKSFORME

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

Description

[Darkspirit]

Attachment: aboutsupport.txt

Win 10, GTX 1060
I had http://us.download.nvidia.com/Windows/411.63/411.63-win10-win8-win7-desktop-release-notes.pdf (and other tabs) opened and made a driver upgrade from 399.07 to 411.63.
After my window went black for a moment to activate the new driver, the pdf viewer did not recover properly and Nightly had a fallback to Basic compositing.

Some quotes:
> WEBRENDER:
> opt-in by default: WebRender is an opt-in feature
> available by user: Force enabled by pref
> unavailable by runtime: Failed to render WebRender
> ADVANCED_LAYERS:
> failed by runtime: Failed initializing MLGDeviceD3D11

> Failure Log
> (#0): GP+[GFX1-]: GFX: RenderThread detected a device reset in BeginFrame
> (#279): CP+[GFX1]: Failed to create software bitmap: Size(1020,1320) Code: 0x8899000c
> (#280): CP+[GFX1]: Failed to create software bitmap: Size(1020,1320) Code: 0x8899000c

Comment 1

[Darkspirit]

Attachment: Screenshot.png

Comment 2

[Darkspirit]

> After my window went black

my display*

Comment 3

[Sotaro Ikeda [:sotaro]]

:darkspirit, what happens with same STR without WebRender?

Comment 4

[Darkspirit]

Attachment: advancedlayers.png

Same profile, but with gfx.webrender.force-disabled;true.
I downgraded from 411.63 to 399.07 while having the pdf opened.
The broken document is black instead of grey.

> Compositing: Direct3D 11 (Advanced Layers)

> Failure Log
> (#0): GP+[GFX1-]: GFX: D3D11 detected a device reset in ResizeBuffers
> (#1): GP+[GFX1-]: Could not resize the swapchain (0x5b6,0x487)
> (#2): GP+[GFX1-]: Could not resize the swapchain (0x5b6,0x487)

Comment 5

[Darkspirit]

So Advanced Layers did not fallback to Basic, but still had a broken pdf viewer.

Comment 6

[Darkspirit]

Still gfx.webrender.force-disabled;true.
Now I upgraded from 399.07 back to 411.63. This time the pdf reader recovered correctly while getting the same failure log.