Bug#642537: iceweasel: randomly crashes by receiving from X the following: ABORT: Request 155.34: BadLength

[Mike Hommey]

On Fri, Sep 23, 2011 at 11:54:40AM -0400, Cengiz Gunay wrote:
> Package: iceweasel
> Version: 6.0.2-1
> Severity: important
> 
> 
> After having to upgrade iceweasel (because of dependency requirements) to either 5.* or to 6.* it started
> randomly crashing. It runs for a few minutes and then I receive this error on the console:
> 
> ###!!! ABORT: Request 155.34: BadLength (poly request too large or
> internal Xlib length error); 215 requests ago: file
> /build/buildd-iceweasel_6.0.2-1-i386-0rGvYM/iceweasel-6.0.2/toolkit/xre/nsX11ErrorHandler.cpp,
> line 199
> 
> To make sure it's not the add-ons, I ran it like this:
> MOZILLA_DISABLE_PLUGINS=1 gdb --args /usr/lib/iceweasel/firefox-bin -g -safe-mode
> 
> And got the stack trace:
> (gdb) bt full 
> #0  0xb74d3667 in raise () from /lib/i386-linux-gnu/libc.so.6
> No symbol table info available.
> #1  0xb74d6a52 in abort () from /lib/i386-linux-gnu/libc.so.6
> No symbol table info available.
> #2  0xb773bee7 in mozalloc_abort (msg=0xbfc5c454 "###!!! ABORT: Request
> 155.34: BadLength (poly request too large or internal Xlib length
> error); 215 requests ago: file
> /build/buildd-iceweasel_6.0.2-1-i386-0rGvYM/iceweasel-6.0.2/toolkit/xre/nsX11Erro"...)
> at
> /build/buildd-iceweasel_6.0.2-1-i386-0rGvYM/iceweasel-6.0.2/memory/mozalloc/mozalloc_abort.cpp:76
> No locals.
> Die: DW_TAG_unspecified_type (abbrev = 24, offset = 213332010)
> 	has children: FALSE
> 		attributes:
> 				DW_AT_name (DW_FORM_strp) string:
> 				"decltype(nullptr)"
> 				Dwarf Error: Cannot find type of die [in
> 				module
> 				/usr/lib/debug/usr/lib/xulrunner-6.0/libxul.so]
> 
> It's obviously not coming from iceweasel, but I don't
> have any clue on what package to change to fix this problem. I already upgraded
> my Xorg packages.
> 
> I would appreciate if you can give me any insight (I assume it's some
> package I stupidly forgot to upgrade)

Try running iceweasel --sync, it should make X requests synchronously,
which would get you a meaning full backtrace.

Mike