Thanks for that link. It looks related but I'm not sure that it's the fix we need, because I don't think Mozilla uses XCreate* functions from more than 1 thread.
I'd be interested to hear if anyone is seeing the crash with a libX11 built without xcb. (This can be checked with "ldd /usr/lib*/libX11.so | grep xcb".)
All the stacks that I've seen here have libX11 built using libxcb.
All the stacks that I've seen involve a Create function that uses XAllocID. Usually the result of XAllocID is assigned to local variables in the Create function called "pid" as well as "req->pid" (and would be returned on success).
It could be useful to know what value either of these variables hold if this information can be obtained using a debugger after breaking on gdk_x_error.
(In reply to comment #22) osdir.com/ ml/freedesktop. xcb/2008- 04/msg00071. html cgit.freedeskto p.org/xorg/ lib/libX11/ commit/ ?id=cc19618d2eb 3ed92a0b574aee2 6a7da8b4aed5d2
> ...however, I suspect this was tracked down already in March (though ignored
> until November):
> http://
> http://
Thanks for that link. It looks related but I'm not sure that it's the fix we need, because I don't think Mozilla uses XCreate* functions from more than 1 thread.
I'd be interested to hear if anyone is seeing the crash with a libX11 built without xcb. (This can be checked with "ldd /usr/lib*/libX11.so | grep xcb".)
All the stacks that I've seen here have libX11 built using libxcb.
All the stacks that I've seen involve a Create function that uses XAllocID. Usually the result of XAllocID is assigned to local variables in the Create function called "pid" as well as "req->pid" (and would be returned on success).
It could be useful to know what value either of these variables hold if this information can be obtained using a debugger after breaking on gdk_x_error.