Re: firefox in VNC: firefox.core

[Robert Swindells <rjs%fdy2.co.uk@localhost>]

I wrote:
>Thomas Klausner <wiz%NetBSD.org@localhost> wrote:
>>For a couple days/weeks now, whenever I start firefox
>>86.0.1/NetBSD-9.99.81/amd64 in a vnc window, I see:
>>
>>Crash Annotation GraphicsCriticalError: [0][GFX1-]: No GPUs detected via PCI (t=0.228558) [GFX-1]: No GPUs detected via PCI
>>Crash Annotation Graphicscriticalerror: [0][GFX1-]: No GPUs detected via PCI (t=0.228558) [1][GFX1-]: glxtest: process failed (received signal 11) (t=0.228639) [GFX1-]: glxtest: process failed (received signal 11)
>>
>>Except for that warning (and the core dump), firefox seems to work fine.
>
>The glxtest() function gets run in a forked copy of Firefox, it is the
>fork that is dumping core.
>
>Maybe our pthreads implementation doesn't work across a fork(2).
>
>I thought that use of TLS had been turned off in Mesa though.
>
>I had some local patches to disable all of this but the source changed
>so they would no longer apply, they disabled WebGL completely.

Another approach could be to patch Firefox to disable the call to
glxtest() but hard-code it to thinking that the test succeded.