Re: webgl regression in firefox >= 111

[Paul Ripke <stix%stix.id.au@localhost>]

On Fri, Aug 25, 2023 at 08:50:06PM +0100, David Brownlee wrote:
> On Thu, 10 Aug 2023 at 09:05, David Brownlee <abs%absd.org@localhost> wrote:
> >
> > On Thu, 10 Aug 2023 at 08:19, nia <nia%netbsd.org@localhost> wrote:
> > >
> > > Does setting webgl.force-enabled work?
> >
> > Doesn't appear to help - with that set https://get.webgl.org/ stderr
> > has the same batch of
> >
> > Crash Annotation GraphicsCriticalError: |[0][GFX1]:
> > MethodDispatcher<7> not found. Please file a bug! (t=4.61454)
> > |[1][GFX1]: DispatchCommand(id: 7) failed.
> >
> > lines and no webgl display in window, though it continues to state
> > "Your browser supports WebGL"
> 
> Just confirming the issue is still present in 116.0.3, and the
> https://bugzilla.mozilla.org/show_bug.cgi?id=1847738 bug has been
> (reasonably from mozilla's perspective) triaged as "not blocking".
> 
> I wonder what would be the best way to approach this - bisect firefox
> source between 110 and 111 to identify the particular change and patch
> around it? Certainly the log lines "cannot access /sys/bus/pci" should
> be feasible to track...

Since I wanted Onshape, and I didn't see any activity here...
I did a little debugging on this, and posted my findings to the bug.
tl;dr: a workaround is to set the pref 'webgl.out-of-process' to false
in about:config.

-- 
Paul Ripke
"Great minds discuss ideas, average minds discuss events, small minds
 discuss people."
-- Disputed: Often attributed to Eleanor Roosevelt. 1948.