Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 549247 - [abrt] crash in gstreamer-0.10.25.1-2.fc13
Summary: [abrt] crash in gstreamer-0.10.25.1-2.fc13
Keywords:
Status: CLOSED DUPLICATE of bug 548989
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:182906d9326f5586b1df56f299f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-21 03:29 UTC by Peng Huang
Modified: 2009-12-21 12:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-21 12:18:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (deleted)
2009-12-21 03:29 UTC, Peng Huang 		no flags Details
View All

Description Peng Huang 2009-12-21 03:29:48 UTC 
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)
Comment 1 Peng Huang 2009-12-21 03:29:51 UTC 
Created attachment 379546 [details]
File: backtrace
Comment 2 Peng Huang 2009-12-21 03:39:56 UTC 
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 .
Comment 3 Peng Huang 2009-12-21 04:42:18 UTC 
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.
Comment 4 Peng Huang 2009-12-21 07:24:28 UTC 
I downgraded glibc from 2.11.90-4 to 2.11-4. This problem disappeared.
It seems the problem is in pthread library.
Comment 5 Lennart Poettering 2009-12-21 12:18:19 UTC 

*** This bug has been marked as a duplicate of bug 548989 ***
Note You need to log in before you can comment on or make changes to this bug.