Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true widget.dmabuf-webgl.enabled=false media.hardware-video-decoding.enabled=false webgl.out-of-process.async-present.force-sync=true gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
Bug 1845765 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true widget.dmabuf-webgl.enabled=false media.hardware-video-decoding.enabled=false webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true * This and above pref ensure OpenGL is not used on multiple threads. bug 1777849 comment 21 affected X11, but Mesa itself is neither fully thread safe IIUC. Firefox blocks THREADSAFE_GL by default only for Nouveau. IIRC there was a comment that Radeon is neither fully thread safe. I assume llvmpipe has the same problem. I don't understand why slightly better beformance is traded against security risks by using OpenGL in multiple threads in the same process. widget.dmabuf-webgl.enabled=false media.hardware-video-decoding.enabled=false webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
(I'm just a tester, not a programmer.) Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true * This and above pref ensure OpenGL is not used on multiple threads. bug 1777849 comment 21 affected X11, but Mesa itself is neither fully thread safe IIUC. Firefox blocks THREADSAFE_GL by default only for Nouveau. IIRC there was a comment that Radeon is neither fully thread safe. I assume llvmpipe has the same problem. I don't understand why slightly better beformance is traded against security risks by using OpenGL in multiple threads in the same process. widget.dmabuf-webgl.enabled=false media.hardware-video-decoding.enabled=false webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
(I'm just a tester, not a programmer.) Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true * This and above pref ensure OpenGL is not used on multiple threads. bug 1777849 comment 21 affected X11, but Mesa itself is neither fully thread safe IIUC. Firefox blocks THREADSAFE_GL by default only for Nouveau. IIRC there was a comment that Radeon is neither fully thread safe. I assume llvmpipe has the same problem. I don't understand why better peformance under load is traded against security risks by using OpenGL in multiple threads in the same process. widget.dmabuf-webgl.enabled=false media.hardware-video-decoding.enabled=false webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
(I'm just a tester, not a programmer.) Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true * This and above pref ensure OpenGL is not used on multiple threads. bug 1777849 comment 21 affected X11, but Mesa itself is neither fully thread safe IIUC. Firefox blocks THREADSAFE_GL by default only for Nouveau. IIRC there was a comment that Radeon is neither fully thread safe. I assume llvmpipe has the same problem. I don't understand why better performance under load is traded against security risks by using OpenGL in multiple threads in the same process. widget.dmabuf-webgl.enabled=false media.hardware-video-decoding.enabled=false webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
(I'm just a tester, not a programmer.) Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true * This and above pref ensure OpenGL is not used on multiple threads. bug 1777849 comment 21 affected X11, but Mesa itself is neither fully thread safe IIUC. Firefox blocks THREADSAFE_GL by default only for Nouveau. IIRC there was a comment that Radeon is neither fully thread safe. I assume llvmpipe has the same problem. I don't understand why better performance under load is traded against security risks(?) by using OpenGL in multiple threads in the same process. widget.dmabuf-webgl.enabled=false media.hardware-video-decoding.enabled=false webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
(I'm just a tester, not a programmer.) Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true * This and above pref ensure OpenGL is not used on multiple threads. bug 1777849 comment 21 affected X11, but Mesa itself is neither fully thread safe IIUC. Firefox blocks THREADSAFE_GL by default only for Nouveau. IIRC there was a comment that Radeon is neither fully thread safe. I assume llvmpipe has the same problem. I don't understand why better performance under load is traded against security risks(?) by using OpenGL in multiple threads in the same process. widget.dmabuf-webgl.enabled=false * (IIUC: copies WebGL frames (WebGL -> system memory -> WebRender GL) instead of sharing their GPU buffers) * shouldn't be needed because `LIBGL_ALWAYS_SOFTWARE=1 mozregression --launch 2023-07-24 -a about:support --pref gfx.webrender.all:true` contains DMABUF: Failed to configure + FEATURE_FAILURE_NO_DRM_DEVICE media.hardware-video-decoding.enabled=false * shouldn't be needed because `LIBGL_ALWAYS_SOFTWARE=1 mozregression --launch 2023-07-24 -a about:support --pref gfx.webrender.all:true` contains HARDWARE_VIDEO_DECODING: Force disabled by gfxInfo + FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false
(I'm just a tester, not a programmer.) Mesa d3d12 is for the "Windows Subsystem for Linux" (Linux on top of Windows), it's irrelevant for regular Linux desktops, but it has caused regressions like bug 1804030 (llvmpipe was unaffected + probably introduced with 22.3.0) which has been fixed in [Mesa 22.3.1]( https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa). Ubuntu 22.04 jammy has Mesa [22.2.5](https://packages.ubuntu.com/jammy-updates/libegl-mesa0) and should be unaffected from that specific bug. Does llvmpipe still crash if you set these prefs? webgl.use-canvas-render-thread=false webgl.threadsafe-gl.force-disabled=true * This and above pref ensure OpenGL is not used on multiple threads. bug 1777849 comment 21 affected X11, but Mesa itself is neither fully thread safe IIUC. Firefox blocks THREADSAFE_GL by default only for Nouveau. IIRC there was a comment that Radeon is neither fully thread safe. I assume llvmpipe has the same problem. I don't understand why better performance under load is traded against security risks(?) by using OpenGL in multiple threads in the same process. widget.dmabuf-webgl.enabled=false * (IIUC: copies WebGL frames (WebGL -> system memory -> WebRender GL) instead of sharing their GPU buffers) * Edit: This pref change isn't needed because `LIBGL_ALWAYS_SOFTWARE=1 mozregression --launch 2023-07-24 -a about:support --pref gfx.webrender.all:true` contains DMABUF: Failed to configure + FEATURE_FAILURE_NO_DRM_DEVICE media.hardware-video-decoding.enabled=false * Edit: This pref change isn't needed because `LIBGL_ALWAYS_SOFTWARE=1 mozregression --launch 2023-07-24 -a about:support --pref gfx.webrender.all:true` contains HARDWARE_VIDEO_DECODING: Force disabled by gfxInfo + FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED webgl.out-of-process.async-present.force-sync=true (was needed to avoid bug 1831548) gfx.canvas.accelerated=false gfx.webrender.panic-on-gl-error=true gfx.webrender.multithreading=false