Spencer Janssen on 2007-07-11 19:11:25 -0500:
On Wednesday 11 July 2007 18:39:48 Alec Berryman wrote:
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.
Just tabbed; I can't reproduce it using the tiled layout. To answer Don's question, yes, just fire up glxgears - you can almost see the gears before everything crashes. Works every time. I haven't seen anything similar happen with any other programs, but I don't run much besides iceweasel, urxvt, and emacs. I have reproduced this both on an amd64 with Xinerama and on an i386 without. In both cases I'm running Debian testing with ghc-6.6.1. For some reason the i386 doesn't show a message in ~/.xsession-errors like the one above from the amd64.