[Xmonad] Re: xmonad crashing

Spencer Janssen sjanssen at cse.unl.edu
Wed Jul 11 20:11:25 EDT 2007


On Wednesday 11 July 2007 18:39:48 Alec Berryman wrote:
> Andy Gimblett on 2007-07-11 10:39:44 +0100:
> > On Tue, Jul 10, 2007 at 08:11:02PM +0200, Tassilo Horn wrote:
> > > >>  Indeed, further testing indicates that it only occurs when I am
> > > >>  using the Tabbed layout.
> > >
> > > I think it's the same here, but I'm not exactly sure.
> >
> > I'd like to add my voice and report that I've been experiencing
> > intermittent crashing too, as of the last few days (perhaps since the
> > weekend?).
>
> I updated for the first time in several days and can reliably crash
> xmonad by running glxgears.  I haven't run glxgears in a while, but I
> have run it in the past few weeks with xmonad and neither crashed.
>
> I am seeing a slightly different error, though; instead of an error on
> free() as in the original report, xmonad dies on a munmap_chunk:
>
> *** glibc detected *** xmonad: munmap_chunk(): invalid pointer:
> 0x000000000045b9c0 *** ======= Backtrace: =========
> /lib/libc.so.6(cfree+0x1b6)[0x2ac3f68fe816]
> /usr/lib/libX11.so.6(XFree+0x9)[0x2ac3f5fee4d9]
> xmonad[0x478498]
>
> Additionally, this error happens if I run glxgears, not if I try to
> close it, as some of the others have reported.  When running with dwm, I
> don't see the same crash.

For which layouts does this occur?  Just Tabbed?  Every layout?  We must have 
a double or otherwise invalid free somewhere.


Cheers,
Spencer Janssen


More information about the Xmonad mailing list