Fallback to Basic compositing on a driver update
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | affected |
People
(Reporter: jan, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: nightly-community)
Attachments
(1 file)
|
19.05 KB,
text/plain
|
Details |
(bug 1492871 was about PDF in the past.)
Win10, GTX1060
I made a driver update from 411.63 to 417.71.
Actual: Fallback to Basic compositing (without any crash).
Expected: WR should recover.
Attached about:support still shows the old driver version as I haven't restarted Nightly yet.
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
(#35): GP+[GFX1-]: wr_renderer_render: Shader(Compilation("ps_text_run", ""))
(#36): GP+[GFX1-]: wr_renderer_render: Shader(Compilation("brush_blend", ""))
(#37): GP+[GFX1-]: wr_renderer_render: Shader(Compilation("brush_solid", ""))
(#38): GP+[GFX1-]: wr_renderer_render: Shader(Compilation("brush_image", ""))
(#39): GP+[GFX1-]: wr_renderer_render: Shader(Compilation("brush_image", ""))
(#40): GP+[GFX1-]: Failed to make render context current during destroying.
(#41) Error: Compositors might be mixed (5,1)
(#42): GP+[GFX1]: Failed to create ID3D11Buffer.
(#43): GP+[GFX1-]: [D3D11] CreateInputLayout failed: 0x887a0005
(#44): GP+[GFX1-]: [D3D11] failed to get compositor device attachments
(#45): GP+[GFX1-]: [D3D11] Failed to init compositor with reason: FEATURE_FAILURE_D3D11_INPUT_LAYOUT
(#46): GP+[GFX1-]: [D3D11] failed to get compositor device attachments
(#47): GP+[GFX1-]: [D3D11] Failed to init compositor with reason: FEATURE_FAILURE_D3D11_INPUT_LAYOUT
(#48): GP+[GFX1-]: [D3D11] failed to get compositor device attachments
(#49): GP+[GFX1-]: [D3D11] Failed to init compositor with reason: FEATURE_FAILURE_D3D11_INPUT_LAYOUT
|
Reporter | |
Comment 1•6 years ago
|
||
|
||
Comment 2•6 years ago
|
||
Does the WebRender disabled/D3D11 layers enabled survive a driver update? Or do we fall back to basic there too?
|
|
||
Updated•6 years ago
|
|
|
Reporter | |
Comment 3•6 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #2)
Does the WebRender disabled/D3D11 layers enabled survive a driver update? Or do we fall back to basic there too?
Direct3D 11 (Advanced Layers) did not fall back to Basic.
With WebRender force-disabled:
Description: NVIDIA GeForce GTX 1060 3GB
Vendor ID: 0x10de
Device ID: 0x1c02
Driver Version: 25.21.14.1771
Driver Date: 1-11-2019
Failure Log
(#0) GP+[GFX1-]: GFX: AL_D3D11 abandoned sync
(#1) GP+[GFX1-]: GFX: D3D11 detected a device reset in Present
(#2) GP+[GFX1-]: D3D11 swap chain failed to present: 0x887a0005
Displayed driver version was not updated by F5. After restarting Nightly:
Driver Version: 25.21.14.1881
Driver Date: 1-30-2019
|
|
Reporter | |
Comment 4•6 years ago
|
||
Win10 1809
Updated from
Description: NVIDIA GeForce GTX 1060 3GB
Vendor ID: 0x10de
Device ID: 0x1c02
Driver Version: 25.21.14.1881
Driver Date: 1-30-2019
to
Driver Version: 25.21.14.1967
Driver Date: 3-17-2019
and did not encounter a fallback to Basic compositing.
Description
•