Update from 82.0b6 to 82.0b7 results "Direct3D 11". It should be "Direct3D 11 (Advanced Layers)"
Categories
(Core :: Graphics: Layers, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox82 | --- | affected |
People
(Reporter: alice0775, Unassigned)
References
Details
Attachments
(3 files)
Using GPU which is not WEBRENDER_QUALIFIED.
Steps To Reproduce:
- Start Firefox82.0b6 with new profile
--- observe Graphics section of about:support
WebRender is enabled as expected due to early beta - And update to Firefox82.0b7(or later) with the same profile of step1
--- observe Graphics section of about:support
Graphics compositing is "Direct3D 11" - Start Firefox82.0b7 with new profile
--- observe Graphics section of about:support
Graphics compositing is "Direct3D 11 (Advanced Layers)"
Actual Results:
If update b6 to b7(or later) "Advanced Layers" is disabled.
It means that layers.mlgpu.sanity-test-failed doesn't seem to be initializing (retesting).
After removing layers.mlgpu.sanity-test-failed from prefs.js then "Advanced Layers" is enabled as expected.
Expected Results:
"Advanced Layers" should be enabled.
| Reporter | ||
Comment 1•5 years ago
|
||
| Reporter | ||
Comment 2•5 years ago
|
||
| Reporter | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Comment 5•5 years ago
|
||
Never mind, early beta ended. Although I don't see it in the pushlog which is strange. But according to the scheduled this is expected with an Evergreen "Beta 6 early betas end October 2".
WRT to losing advanced layers, I'm not sure how the sanity test works, I'll take a quick look.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
Looks like we could explicitly disable it if we ever gave you WR:
https://searchfox.org/mozilla-central/source/toolkit/components/gfx/SanityTest.jsm#215
We probably should be ensuring we do something similar to:
https://searchfox.org/mozilla-central/source/gfx/thebes/gfxWindowsPlatform.cpp#383
For early beta switchover.
Comment 7•5 years ago
|
||
Comment 8•5 years ago
|
||
I think this might be happening for users that get blocked by bug 1678942
Updated•4 years ago
|
Description
•