sw-wr: Don't use DMABUF when Software WebRender is active
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | disabled |
People
(Reporter: jan, Assigned: aosmond)
References
(Blocks 2 open bugs)
Details
(Keywords: nightly-community)
Attachments
(1 file)
Gnome Wayland, Debian Testing
WebGL (widget.dmabuf-webgl.enabled) is grey, Video is green:
MOZ_X11_EGL=1 mozregression --launch 20201001094020 --pref gfx.webrender.all:true gfx.webrender.software:true media.ffmpeg.dmabuf-textures.enabled:true -a https://webglsamples.org/aquarium/aquarium.html -a https://bug1619882.bmoattachments.org/attachment.cgi?id=9149605
|
||
Comment 2•4 years ago
|
||
Once bug 1668713 lands, then we can change the two callsites that return TextureType::DMABUF to check for TextureFactoryIdentifier::mUsingSoftwareWebRender.
|
||
Updated•4 years ago
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 3•4 years ago
|
||
Pushed by aosmond@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c21b64c6ceea Disable DMABUF with software WebRender. r=mattwoodrow
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
|
Reporter | |
Comment 6•4 years ago
|
||
MOZ_X11_EGL=1 mozregression --launch c21b64c6ceea --pref gfx.webrender.all:true gfx.webrender.software:true media.ffmpeg.dmabuf-textures.enabled:true -a https://webglsamples.org/aquarium/aquarium.html -a https://bug1619882.bmoattachments.org/attachment.cgi?id=9149605
Not entirely fixed: Video is still green.
(In general, could you check if DMABUF is correctly wired up? There are bugs like bug 1641603/bug 1666099.)
|
|
Assignee | |
Comment 7•4 years ago
|
||
MOZ_X11_EGL=1 mozregression --find-fix --bad 2020-10-16 --good 2020-11-13 --pref gfx.webrender.all:true gfx.webrender.software:true media.ffmpeg.dmabuf-textures.enabled:true -a https://webglsamples.org/aquarium/aquarium.html -a https://bug1619882.bmoattachments.org/attachment.cgi?id=9149605
I thought I tested both at the time. In any event, the secondary issue was fixed by bug 1675453.
Description
•