That's forcing us to take a whole new code path which clearly we're just discovering is a bit buggy on some platforms.
To work around it, you can export:
WEBKIT_DMABUF_RENDERER_FORCE_SHM=1
which should have better performance than another workaround:
WEBKIT_DISABLE_DMABUF_RENDERER=1
Both of those also solve bug 2060938 and bug 2062146 which I suspect is a newer crash caused by the newer Mesa in Noble. So if people find the installer is reliably crashing recently then that might explain it.
I have a hunch the problems might have started in WebKit 2.43.2 which included a backport of: /github. com/WebKit/ WebKit/ commit/ 8b0ce3683045d93 cd365e91a4299f7 e9babfc126
https:/
That's forcing us to take a whole new code path which clearly we're just discovering is a bit buggy on some platforms.
To work around it, you can export:
WEBKIT_ DMABUF_ RENDERER_ FORCE_SHM= 1
which should have better performance than another workaround:
WEBKIT_ DISABLE_ DMABUF_ RENDERER= 1
Both of those also solve bug 2060938 and bug 2062146 which I suspect is a newer crash caused by the newer Mesa in Noble. So if people find the installer is reliably crashing recently then that might explain it.