Bug 18063

Summary:	_XCBUnlockDisplay: Assertion ... failed
Product:	XCB	Reporter:	Joerg Morbitzer <jomo>
Component:	Library	Assignee:	Jamey Sharp <jamey>
Status:	RESOLVED WORKSFORME	QA Contact:	xcb mailing list dummy <xcb>
Severity:	normal
Priority:	medium
Version:	1.1
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Joerg Morbitzer 2008-10-14 08:23:23 UTC

Hi all,

we are running many Debian Linux machines (Lenny, 64 Bit version). Occasionally on one PC a proprietary X-Client application is crashing, printing this into logfile as the very last m
essage:

../../src/xcb_lock.c:33: _XCBUnlockDisplay: Assertion `xcb_get_request_sent(dpy->xcb->connection) == dpy->request' failed.

The version of the XCB libraries for Debian Lenny are 1.1 :

sol3@wks-lnx16:~$ dpkg -l | grep xcb
ii  libxcb-render-util0                  0.2.1+git1-1               utility libraries for X C Binding -- render-util
ii  libxcb-render0                       1.1-1.1                    X C Binding, render extension
ii  libxcb-xlib0                         1.1-1.1                    X C Binding, Xlib/XCB interface library
ii  libxcb1                              1.1-1.1                    X C Binding
sol3@wks-lnx16:~$

The X-Server is version 1.4.2, it uses the latest 64 Bit Nvidia driver 177.80 (if this is important for you).

The affected X client application is under heavy load (lot of CPU usage in the background and a lot of 2D updates to the X server).

Does anybody know what the problem might be? If I ask Mrs. Google just for "XCBUnlockDisplay" I get two(!) replies only :-( !

Any help is welcome,

thanks in advance, Joerg.

Comment 1 Joerg Morbitzer 2008-12-04 07:32:54 UTC

Hi,

we now took the libx11-6 sources from Debian, compiled a new libX11.so.6.2.0 using the configure command "--without-xcb" and adjusted the LD_LIBRARY_PATH to point to this new lib instead of the default one located in /usr/lib/ --> since then our application runs absolutely stable! So there is definately something strange going on with XCB...


Kind regards, Joerg.

Comment 2 Jamey Sharp 2009-10-09 08:58:02 UTC

Sorry to have dropped this report. Since that assertion is gone with the socket-handoff work, which has been in Debian for some time now, has your problem gone away?

Comment 3 Joerg Morbitzer 2009-10-14 01:44:17 UTC

bugzilla-daemon@freedesktop.org wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=18063
> 
> 

Hi Jamey,

since version 1.1-1.2 (shipped with the latest Debian Lenny) it looks
like this bug is nearly gone, it happens occasionally only, roughly once
every 2 months instead of once of twice a day.

Once we have upgraded to the new Debian Squeeze later this year, using
xbc-libs 1.4-1 or something, I will let you know the results.

Kind regards, Joerg.

> Jamey Sharp <jamey@minilop.net> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           QAContact|                            |xcb@lists.freedesktop.org
> 
> 
> 
> 
> --- Comment #2 from Jamey Sharp <jamey@minilop.net>  2009-10-09 08:58:02 PST ---
> Sorry to have dropped this report. Since that assertion is gone with the
> socket-handoff work, which has been in Debian for some time now, has your
> problem gone away?
> 
>

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.