| 2011-06-22 17:59:39 |
Eliah Kagan |
description |
Binary package hint: audacious
Audacious2 usually quits with no problems, but occasionally it hangs on exit. 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, package version 1:2010.8.8-0ubuntu1). 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
After previous crashes, I submitted this bug as Bug 688599, but the friendly "Apport retracing service" bot marked it Invalid because it did not have a usable stack trace, suggesting that I upgrade some package versions (which required that I add maverick-proposed to /etc/sources.list). I did that, and then submitted the bug report again (as per the instructions of "Apport retracing service") as Bug 690432, but the stack trace for that didn't look so good either, and I noticed that I had neglected to install audacious-dbg for the debug symbols. Hoping that it would help, I installed audacious-dbg after that, and waited for the crash to occur again. This report is for that third crash, and the stack trace still doesn't look very good, but unless someone can give me advice on how to improve it, this is the probably the best I can get, so I marked the second bug report Invalid as well, to be supreseded by this bug report.
When I tell audacious to quit, it doesn't appear to crash immediately--it hangs for a while first. The first two times, I waited a while and sent SIGTERM, which appeared to prompt this crash. This time, I just waited longer, and the crash occurred by itself. It might be that the crash always occurs immediately, and that the "hanging" is actually just the time it takes for Apport to collect data.
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: Thu Dec 16 20:07:13 2010
Disassembly: => 0x7f21bb5d4286: Cannot access memory at address 0x7f21bb5d4286
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: 0x7f21bb5d4286: Cannot access memory at address 0x7f21bb5d4286
PC (0x7f21bb5d4286) 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 |
Binary package hint: audacious
Audacious2 usually quits with no problems, but occasionally it crashes on exit with SIGSEGV in __lll_lock_wait(). Since audacious2 often has a large number of threads, it takes a long time for Apport to generate a .crash file, during which time the interface is frozen--therefore, it is easy to mistake this crash for a hang. But audacious2 does terminate by itself, without user intervention, every time.
I first reported this with audacious 2.4.0-0ubuntu3 on Maverick amd64 (see original description, duplicate bug 688599, and duplicate bug 690432). I have subsequently gotten this crash with audacious 2.4.4-1 on Natty amd64 on the same physical machine (see duplicate bug 800078). I have never gotten a useful stack trace with Apport, but I got some mediocre manual traces in gdb on the Maverick system (https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/691378/comments/7 is the best). If I get a trace in Natty that's as good or better, I'll post it and edit this to link to it.
Please note that the original description and a number of comments below suggest that this problem may be related to an input-output bug in the Linux kernel. That may be the case, and many of the times this crash occurred was when the machine was under heavy I/O. However, I have found that the situation in the original report--where my music library was on an external hard drive that may have been malfunctioning--is not necessary to produce this problem. While in all cases the music library was on a partition or network drive mounted as a fuse filesystem (ntfs-3g originally, and now mount.cifs), that may or may not be relevant.
Since Apport is always entirely unsuccessful backtracing this bug, the original title was "audacious2 crashed with SIGSEGV". I have edited the title to reflect specific information from the manual traces.
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: Thu Dec 16 20:07:13 2010
Disassembly: => 0x7f21bb5d4286: Cannot access memory at address 0x7f21bb5d4286
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: 0x7f21bb5d4286: Cannot access memory at address 0x7f21bb5d4286
PC (0x7f21bb5d4286) 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 |
|
