<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - DRI3 rendering gets stuck waiting for present idle notify event" href="https://bugs.freedesktop.org/show_bug.cgi?id=84252#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - DRI3 rendering gets stuck waiting for present idle notify event" href="https://bugs.freedesktop.org/show_bug.cgi?id=84252">bug 84252</a> from <a class="email" href="mailto:liquid.acid@gmx.net" title="Tobias Jakobi <liquid.acid@gmx.net>"> Tobias Jakobi</a> <pre>Hello Axel, thanks for the explanation. So if I understand this correctly, then this issues comes from the fact that each XCB connection object is protected by a (single) mutex (the iolock one, if I read the libxcb code correctly), which causes trouble in Mesa' GLX DRI3 implementation because the same XCB connection is then used from two different threads. One thread A uses the connection to wait for one event, which doesn't come because thread B is blocked (XCB mutex is locked) and therefore never reaches the point where the event is signalled. I had a brief look at the Xnine implementation and the GLX DRI3 one, but I'm not too familiar with it to port the "two connection" approach over.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>