After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 610187 - [xvimagesink] making X calls with x_lock unlocked
[xvimagesink] making X calls with x_lock unlocked
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-16 19:34 UTC by Tommi Komulainen
Modified: 2011-06-24 19:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Make X calls with x_lock locked (1.67 KB, patch)
2010-02-16 19:34 UTC, Tommi Komulainen 		none Details | Review

Description Tommi Komulainen 2010-02-16 19:34:47 UTC 
Created attachment 153956 [details] [review]
Make X calls with x_lock locked

Saw the following assertion a couple times.

../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy->request)) >= 0)' failed.

Can't get better backtrace as attaching gdb to the process manages to freeze the whole device - possibly self inflicted problem, nevermind that.

Anyway, according to google that assertion could suggest threading problem and reading the code I noticed a few potential places where X calls are made without x_lock held and without any comments clarifying why it would be safe to do so.

Take with grain of salt, I haven't tried building yet as I'm missing build dependencies :-/
Comment 1 Sebastian Dröge (slomo) 2011-05-09 10:00:23 UTC 
Is this still a problem with the latest versions of everything? And can you confirm now that your patch fixes it?