WebRender driver block list on Linux needs to be refactored to allow by default
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox108 | --- | fixed |
People
(Reporter: ahale, Assigned: aosmond)
References
Details
Attachments
(3 files)
As much as possible we should be giving Linux users the happy path of fast WebRender, so we should change the block list to an allow by default policy, rather than enabling each piece of hardware only on request (e.g. bug #1791970).
Changing to an allow by default policy will likely reveal some broken configurations out there, so this may involve multiple attempts to get it right.
A second factor is that users who previously encountered graphics bugs may have been automatically punted to software WebRender and we need to put their prefs back to accelerated by default, as this is not a setting that is obvious to users and may simply lead to the perception that Firefox is slow, long after the underlying driver bugs were fixed.
Reporter | ||
Comment 1•2 years ago
|
||
NI - I'd like to know more about any major quirks in this block list code to minimize breakage when changing it to allow by default, thanks :)
Reporter | ||
Comment 2•2 years ago
|
||
https://searchfox.org/mozilla-central/rev/f118dae98073bc17efb8604a32abfcb7b4e05880/widget/gtk/GfxInfo.cpp#629 is the relevant function I am looking at. It's a bit unclear to me how this is evaluated, as it looks like a series of conditions with unknown precedence.
Reporter | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
I'm putting this together. There are lots of things to adjust, add and rip out.
Assignee | ||
Comment 4•2 years ago
|
||
WebRender is a mature feature. We should start blocking it on known bad
devices over allowlisting known good devices. This may enable WebRender
in a few more obscure places than we shipped before.
Assignee | ||
Comment 5•2 years ago
|
||
This is always true.
Assignee | ||
Comment 6•2 years ago
|
||
This is always true.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 8•2 years ago
|
||
Backed out for causing multiple failures on RemoteProcessMonitor
- Backout link
- Push with failures
- Failure Log
- Failure line: PROCESS-CRASH | RemoteProcessMonitor | application crashed [@ mozilla::gfx::gfxConfigManager::ConfigureFromBlocklist(long, mozilla::gfx::FeatureState*)]
Assignee | ||
Comment 9•2 years ago
|
||
I forgot to update the status code for WR on Android:
https://treeherder.mozilla.org/jobs?repo=try&revision=e262f50db7aa9ee098aa4e6501e449da1ac398e5
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f0dd55319351
https://hg.mozilla.org/mozilla-central/rev/f518d5630dee
https://hg.mozilla.org/mozilla-central/rev/adbac17a6db3
Description
•