Red Hat Bugzilla – Bug 598278
[abrt] crash in audacity-1.3.11-0.1.beta.fc13: *** glibc detected *** audacity: invalid fastbin entry (free): 0x08fef648 *** (SIGABRT)
Last modified: 2010-07-15 09:31:12 EDT
abrt 1.1.0 detected a crash.
Attached file: backtrace
comment: Was recording a podcast with standard audio input from a headset mic. About 7 minutes in the program crashed. Dunno if this matters but I had two headsets (both mic and headphones) plugged into slots with a 2 way splitter. I'm totally unsure why it happened.
reason: Process /usr/bin/audacity was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce
1. Havn't reproduced
Created attachment 418427 [details]
The memory management in glibc aborted the program, because it ran into an unexpected/fatal error condition. Call trace is from within wxWidgets -> Pango. As whether it's due to something bad passed in from Audacity, cannot tell with only a brief look at the backtrace.
(In reply to comment #0)
> comment: Was recording a podcast with standard audio input from a headset mic.
> About 7 minutes in the program crashed. Dunno if this matters but I had two
> headsets (both mic and headphones) plugged into slots with a 2 way splitter.
> I'm totally unsure why it happened.
What do you mean by slot ?
Is this 2 usb audio devices ?
or just analog audio into a 'mic in' socket ?
Did the issue recur ?
Have you been using audacity ?
We have updated audacity to 1.3.12-beta which will be available shortly in
Fedora 13 updates testing repo:
yum --enablerepo=updates-testing update audacity
It would be good to hear how you go testing against your original test case,
and provide any positive or negative feedback in the koji update comments at:
By slot I mean standard audio input slot, so yes 'mic in'. The issue has not re-occurred. I've been using audacity for a long time, for this and other things and continue to use audacity for the same purpose from here on, that being recording podcasts. If it happens again I'll bug it again and try to be more concrete.
(In reply to comment #4)
Thanks. Did your /tmp (or wherever you have audacity's temp recording set) or your save location fill up while you were recording ?
I can't say for sure, but I don't think so, because after I restarted the program I continued recording for another 10 minutes (the file was correctly restored up to the moment it crashed).