[prev in list] [next in list] [prev in thread] [next in thread]
List: freedesktop-xcb
Subject: [Xcb] [Bug 22362] New: Socket handoff deadlock
From: bugzilla-daemon () freedesktop ! org
Date: 2009-06-19 8:39:40
Message-ID: bug-22362-13485 () http ! bugs ! freedesktop ! org/
[Download RAW message or body]
http://bugs.freedesktop.org/show_bug.cgi?id=22362
Summary: Socket handoff deadlock
Product: XCB
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Library
AssignedTo: xcb@lists.freedesktop.org
ReportedBy: linuxhippy@gmail.com
QAContact: xcb@lists.freedesktop.org
Created an attachment (id=26950)
--> (http://bugs.freedesktop.org/attachment.cgi?id=26950)
simple test-case demonstrating the deadlock.
When using the new socket-handoff functionality I often encounter deadlocks
inside of xcb.
A lot of discussion happend on the xcb mailinglist, but so far nobody was able
to explain what exactly happens, nore what the problem is. It could be I am
doing something wrong, but since there is no documentation at all ... who
knows.
I tried myself to understand the problem, but my experience with posix/c is
quite limited :-/
Attached is a simple single-threaded test-case which triggers the problem.
It would be really great if this could be fixed soon, Java would like to use
self-generated protocol to speed up its rendering sooner than later ;)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
_______________________________________________
Xcb mailing list
Xcb@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xcb
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic