Bug 924573

Summary: [abrt] alsa-utils-1.0.26-1.fc18: pa_mutex_free: Process /usr/bin/aplay was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: prasanjit
Component: alsa-utilsAssignee: Jaroslav Kysela <jkysela>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jkysela, kcchouette+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:64b65c14d96f981dba14f24102082b633875b3cc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:11:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description prasanjit 2013-03-22 05:56:48 UTC 
Description of problem:
I was running a heaving ruby on rails application while these errors occurred

Version-Release number of selected component:
alsa-utils-1.0.26-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        aplay -q -c 1 -t raw -f s16 -r 32000 /tmp/audiofile_03530
crash_function: pa_mutex_free
executable:     /usr/bin/aplay
kernel:         3.8.3-203.fc18.x86_64
uid:            1000
var_log_messages: Mar 22 01:51:03 dhcppc6 abrt[3534]: Saved core dump of pid 3532 (/usr/bin/aplay) to /var/spool/abrt/ccpp-2013-03-22-01:51:03-3532 (9605120 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 pa_mutex_free at pulsecore/mutex-posix.c:83
 #3 pa_threaded_mainloop_free at pulse/thread-mainloop.c:131
 #4 pulse_free at pulse.c:187
 #5 pulse_close at pcm_pulse.c:887
 #6 snd_pcm_ioplug_close at pcm_ioplug.c:744
 #7 snd_pcm_close at pcm.c:706
 #8 signal_handler at aplay.c:397
 #11 pthread_cond_wait@@GLIBC_2.3.2 at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:141
 #12 pa_threaded_mainloop_wait at pulse/thread-mainloop.c:206
 #13 pulse_wait_operation at pulse.c:72

Potential duplicate: bug 783856
Comment 1 prasanjit 2013-03-22 05:56:53 UTC 
Created attachment 714307 [details]
File: backtrace
Comment 2 prasanjit 2013-03-22 05:56:56 UTC 
Created attachment 714308 [details]
File: cgroup
Comment 3 prasanjit 2013-03-22 05:56:59 UTC 
Created attachment 714309 [details]
File: core_backtrace
Comment 4 prasanjit 2013-03-22 05:57:01 UTC 
Created attachment 714310 [details]
File: dso_list
Comment 5 prasanjit 2013-03-22 05:57:04 UTC 
Created attachment 714311 [details]
File: environ
Comment 6 prasanjit 2013-03-22 05:57:07 UTC 
Created attachment 714312 [details]
File: limits
Comment 7 prasanjit 2013-03-22 05:57:10 UTC 
Created attachment 714313 [details]
File: maps
Comment 8 prasanjit 2013-03-22 05:57:13 UTC 
Created attachment 714314 [details]
File: open_fds
Comment 9 prasanjit 2013-03-22 05:57:15 UTC 
Created attachment 714315 [details]
File: proc_pid_status
Comment 10 Fedora End Of Life 2013-12-21 12:22:38 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 11 Fedora End Of Life 2014-02-05 20:11:33 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.