audacious2 crashed with SIGSEGV when quitting

[Eliah Kagan]

Binary package hint: audacious

This bug report was previously submitted as Bug 688599, but I did not have the necessary package versions installed to generate a stack trace. This report has a stack trace, but unfortunately I neglected to install the debug symbols for audacious2. I'm filing this report, rather than installing the debug symbols and waiting for the issue to occur again, because the issue occurs rarely enough that it might be some time before it occurs again. All the descriptive information I wrote in Bug 688599 is reproduced here, modified where appropriate. I am reporting this as a new bug (rather than commenting on Bug 688599) as per the instructions of the friendly "Apport retracing service" bot.

Audacious2 usually quits with no problems, but occasionally it hangs on exit. Sending SIGTERM quits it (after a delay of a minute or more), producing this crash. The delay between sending SIGTERM and the audacious window closing might just be the time it takes for Apport to collect information. I am unsure if this is a new bug -- it might be a duplicate of Bug 640732 or Bug 650531 (or others). The bug report summary generated by Apport was just "audacious2 crashed with SIGSEGV", which is different from the summaries for those bugs which appeared to be automatically generated as well. So I decided to play it safe and submit a new bug report.

I'm running audacious 2.4.0-0ubuntu3 on Maverick amd64. My Audacious music library is (mostly) on an external USB drive that occasionally becomes unreadable and has to be powered off and back on again. I suspect there may be a hardware (or driver) problem with that drive and/or USB on this machine. Perhaps that is a factor in producing this error. In case it's relevant, the drive is formatted NTFS (and mounted readwrite with NTFS-3G). In any case, even if the crash is motivated by problems elsewhere in the system, it still probably reflects some bug in Audacious itself. And I am not sure the crash has anything to do with any defects external to Audacious.

In case this crash is triggered by an I/O error, here's the output of "uname -a":
Linux Apok 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: audacious 2.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Tue Dec 14 18:38:03 2010
Disassembly: => 0x7f4f5ba02286: Cannot access memory at address 0x7f4f5ba02286
ExecutablePath: /usr/bin/audacious2
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
ProcCmdline: audacious
ProcEnviron:
 LANGUAGE=en_US.utf8
 LANG=en_US.utf8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4f5ba02286: Cannot access memory at address 0x7f4f5ba02286
 PC (0x7f4f5ba02286) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: audacious
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: audacious2 crashed with SIGSEGV
UserGroups: adm admin cdrom lpadmin plugdev sambashare

[Eliah Kagan (degeneracypressure)]

Looking more closely, my stack trace in this bug report doesn't look so good either. I've installed the debug symbols and just experienced this same crash again. The stack trace still doesn't look very good...but nothing seems to have been done with this bug report so far, so I'm going to mark this as Invalid and submit the new bug report...with *might* have better information.

[Eliah Kagan (degeneracypressure)]

Correction: "with *might have better information" --> "which *might* have better information"