Comment #12 on issue 9869 by valentinej: _XGetXCBBuffer: Assertion `((int)
((xcb_req) - (dpy->request)) >= 0)' failed
http://code.google.com/p/chromium/issues/detail?id=9869
Here's another patch, which initializes the thread system. You also need
to fix
scons to link in gthread, eg. -lgthread-2.0, which I don't know how to do.
I was
able to get it to build by hacking chrome/app.scons, but since the file
seems to
be autogen, that's obviously wrong.
From the stack, it looks like chrome runs gtk out of MessagePumpForUI::Run,
with
calls to g_main_context_iteration() -- however, wrapping gdk thread locks
around
that resulted in deadlock. I don't know a lot about gtk, sorry.
As an aside, gdk's thread system seems particularly poorly thought out. In
particular, there's no mechanism to ask if the lock is held, and hence you
can't
assert it. There are also no relevant asserts on the lock built into the
library.
This sort of assert is really the only reasonable way to debug this sort of
thing,
since you're never going to find everything by crashing.
Attachments:
bug9869-3.diff 3.4 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
