<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - clGetPlatformIDs causes futex race condition" href="https://bugs.freedesktop.org/show_bug.cgi?id=94040#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - clGetPlatformIDs causes futex race condition" href="https://bugs.freedesktop.org/show_bug.cgi?id=94040">bug 94040</a> from <a class="email" href="mailto:currojerez@riseup.net" title="Francisco Jerez <currojerez@riseup.net>"> Francisco Jerez</a> <pre>(In reply to bob from <a href="show_bug.cgi?id=94040#c7">comment #7</a>) > In the specific case of blender, there are 31 hung up threads with around 9 > each waiting on > > __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 > pthread_cond_wait@@GLIBC_2.3.2 () at > ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 > do_futex_wait () at ../sysdeps/unix/sysv/linux/futex-internal.h:205 > > The remaining threads are waiting on poll () at > ../sysdeps/unix/syscall-template.S:84 with the last being the one I provided > a backtrace for. Is there any one you're interested in particular? After > sampling some of the backtraces they seem to be unrelated, either > blender-specific or just mainloops for udev and pulseaudio waiting for > events, but if please let me know if there's any backtraces you'd like Is there any other hung thread showing mesa function calls in the stack trace? That would be particularly interesting. In any case the more backtraces you can provide the better :)</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>