<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Hang when using glWaitSync with multithreaded shared GL contexts" href="https://bugs.freedesktop.org/show_bug.cgi?id=111784#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Hang when using glWaitSync with multithreaded shared GL contexts" href="https://bugs.freedesktop.org/show_bug.cgi?id=111784">bug 111784</a> from <a class="email" href="mailto:pierre-eric.pelloux-prayer@amd.com" title="Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>"> Pierre-Eric Pelloux-Prayer</a> <pre>Created <a href="attachment.cgi?id=145487" name="attach_145487" title="output from gdb">attachment 145487</a> <a href="attachment.cgi?id=145487&action=edit" title="output from gdb">[details]</a> output from gdb Using the env var "GALLIUM_THREAD=0" makes the issue worse (the example hangs at the first iteration). One app thread is stuck at: glWaitSync(_textureUploadFence, 0, GL_TIMEOUT_IGNORED); The other thread is stuck waiting for the first thread to release the mutex. Before waiting for the mutex it made a call to: "_textureUploadFence = glFenceSync(GL_SYNC_GPU_COMMANDS_COMPLETE, 0);" All the mesa internal threads are waiting for work to do.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>