<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Concurrent call to glClientWaitSync results in segfault in one of the waiters." href="https://bugs.freedesktop.org/show_bug.cgi?id=98172#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Concurrent call to glClientWaitSync results in segfault in one of the waiters." href="https://bugs.freedesktop.org/show_bug.cgi?id=98172">bug 98172</a> from <a class="email" href="mailto:shinji.suzuki@gmail.com" title="shinji.suzuki@gmail.com">shinji.suzuki@gmail.com</a> <pre>I need to take my words back. > dtor should be called only by the thread that eliminated the last reference. Looks like glDeleteSync directly calls (or is a macro of?) st_delete_sync_object. If that is true, the reference count on sync-object, if there is, is not respected. Therefore I think mtx_Lock(so->Shared.Mutex) needs to be present in the dtor function as well. I apologize for my oversight.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>