audacious crashed with SIGSEGV

Bug #1180499 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
audacious (Ubuntu)
New
Undecided
Unassigned

Bug Description

On a Quantal i386 system, audacious crashed when quitting. It usually does not crash; I cannot reproduce this deliberately.

Earlier versions of audacious on earlier Ubuntu releases, on this and other machines, and on both i386 and amd64 systems, have crashed for me. So perhaps the problem is triggered by some feature of my music library. It is, and has been, very large -- perhaps larger than the music libraries with which audacious has been tested. In particular, my "main playlist" contains 54261 tracks.

All the previous crashes (each of which was with an older version of audacious on an older Ubuntu release) on quitting appeared to be the same bug. See bug 691378 (and its duplicates). I suspect this may be the same bug as bug 691378. Since (1) the machine on which the crash reported here occurred did not have many debug symbols installed, and (2) this occurs much less frequently than it used to and I'm not sure I can produce it again, I am reporting this. Hopefully Apport retracing service can produce a stack trace with enough detail that it can be compared to at least one of the stack traces posted in bug 691378.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: audacious 3.2.3-1
ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
Uname: Linux 3.5.0-27-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
Date: Wed May 15 13:57:25 2013
Disassembly: => 0xb329092f: Cannot access memory at address 0xb329092f
ExecutablePath: /usr/bin/audacious
InstallationDate: Installed on 2012-08-21 (267 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: audacious
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb329092f: Cannot access memory at address 0xb329092f
 PC (0xb329092f) 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
Stacktrace:
 #0 0xb329092f in ?? ()
 No symbol table info available.
 #1 0xb1da6058 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: audacious crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2013-03-21 (55 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb329092f in ?? ()
 No symbol table info available.
 #1 0xb1da6058 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.