Re: xfwm4 crashes on NetBSD 9.99.17 (was "Re: firefox dumping core after NetBSD upgrade")

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

I've tested xfce4 - a few days old build from -current pkgsrc - now on
real hardware with functional dri2. I get the same as with the
VirtualBox client - I have to disable compositing to get xfwm4
working. At the same time glmark2 returns the usual or close to
results.

The other thing is - firefox used to be able to run WebGL under
-current a few months ago; now it reports that the system does not
support it. With overnight built firefox 70.0 I now get a core every
time I start it up, but then it works fine. The trace is again:
...
(gdb) bt
#0  0x00007ced69a09a41 in pthread_mutex_lock () from /usr/lib/libpthread.so.1
#1  0x00007ced4881c42c in _mesa_error () from
/usr/X11R7/lib/modules/dri/swrast_dri.so
#2  0x00007ced48836816 in _mesa_GetString () from
/usr/X11R7/lib/modules/dri/swrast_dri.so
#3  0x00007ced581475d3 in ?? () from /usr/pkg/lib/firefox/libxul.so
....

Now it seems only epiphany can run WebGL (but has some other problems,
e.g. can't quit from the gui if WebGL was running).

On Sun, 27 Oct 2019 at 23:54, Robert Swindells <rjs%fdy2.co.uk@localhost> wrote:
>
>
> "David H. Gutteridge" <david%gutteridge.ca@localhost> wrote:
> >On Wed, 2019-10-16 at 12:10 +0100, Chavdar Ivanov wrote:
> > On Wed, 16 Oct 2019 at 11:03, David H. Gutteridge <david%gutteridge.ca@localhost
> > > wrote:
> >
> > > FWIW, aside from Firefox (where I also see this issue), I've found
> > > since the recent Mesa upgrade, Xfce4's window manager consistently
> > > crashes during startup. These's a correlation with Firefox in the
> > > backtrace:
> > >
> > > #3  0x000079f26fa5e256 in _mesa_GetString (name=7937) at
> > > /usr/xsrc/external/mit/MesaLib/dist/src/mesa/main/getstring.c:124
> > >         ctx = 0x79f288ae5898
> > >         vendor = 0x79f271833414 "Brian Paul"
> > >         renderer = 0x79f2718214ab "Mesa"
> > > #4  0x000000000041b1b5 in ?? ()
> > > No symbol table info available.
> > > #5  0x0000000000442bb8 in ?? ()
> > > No symbol table info available.
> > > [...]
>
> If you still have the core dump for this, or can generate another, it
> could be helpful to examine the ctx variable in _mesa_GetString() using
> gdb.
>
> If it is like firefox then I think you will find that not all of the
> structure is in mapped memory.
>
> Can only think of two ways this could happen, either the ctx pointer
> itself is garbage or the size given to calloc() to allocate the context
> was too small. Have been trying to work out where this gets allocated
> but not found it yet.
>
> I have got some patches to firefox that let me display Google Maps but
> they basically just disable the use of OpenGL.
>


-- 
----