abrt 1.0.2 detected a crash. How to reproduce ----- 1. gst-launch audiotestsrc ! pulsesink Comment: execute gst-launch audiotestsrc ! pulsesink Attached file: backtrace cmdline: /usr/bin/gst-launch-0.10 audiotestsrc ! pulsesink component: gstreamer executable: /usr/bin/gst-launch-0.10 kernel: 2.6.32.2-14.fc13.i686 package: gstreamer-0.10.25.1-2.fc13 rating: 3 reason: Process was terminated by signal 6 (Aborted)
Created attachment 379546 [details] File: backtrace
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. I think the problem is in pulseaudio .
I put some printf in pulsecore/mutex-posix.c, and use ./thread-mainloop-test to reproduce this problem. It seems crash is caused by thread 0xb786e730 unlock the mutex locked by thread 0xb786db70. [phuang@phuang-notebook src]$ ./thread-mainloop-test Lock thread=0xb786e730 m=0x9942008 Lock thread=0xb786e730 m=0x9942008 OK UnLock thread=0xb786e730 m=0x9942008 UnLock thread=0xb786e730 m=0x9942008 OK Lock thread=0xb786e730 m=0x9942260 Lock thread=0xb786e730 m=0x9942260 OK UnLock thread=0xb786e730 m=0x9942260 UnLock thread=0xb786e730 m=0x9942260 OK Lock thread=0xb786db70 m=0x9942008 Lock thread=0xb786db70 m=0x9942008 OK UnLock thread=0xb786db70 m=0x9942008 UnLock thread=0xb786db70 m=0x9942008 OK Lock thread=0xb786e730 m=0x9942008 Lock thread=0xb786e730 m=0x9942008 OK waiting 5s (signal) Lock thread=0xb786db70 m=0x9942008 Lock thread=0xb786db70 m=0x9942008 OK UnLock thread=0xb786db70 m=0x9942008 UnLock thread=0xb786db70 m=0x9942008 OK Lock thread=0xb786db70 m=0x9942008 Lock thread=0xb786db70 m=0x9942008 OK TIME EVENT START wait completed signal accepted UnLock thread=0xb786e730 m=0x9942008 UnLock thread=0xb786e730 m=0x9942008 FAILED Lock thread=0xb786e730 m=0x99422d8 Lock thread=0xb786e730 m=0x99422d8 OK UnLock thread=0xb786e730 m=0x99422d8 UnLock thread=0xb786e730 m=0x99422d8 OK Assertion 'i == 0' failed at pulsecore/mutex-posix.c:114, function pa_mutex_unlock(). Aborting.
I downgraded glibc from 2.11.90-4 to 2.11-4. This problem disappeared. It seems the problem is in pthread library.
*** This bug has been marked as a duplicate of bug 548989 ***