audacious2 crashed with SIGSEGV in SAD_dither_process_buffer()

[Jörn Horstmann]

Binary package hint: audacious

Ubuntu 9.10 alpha 3, audacious 2.1-1ubuntu1

The crash happened near the end of a song, using the crossfade output plugin.

ProblemType: Crash
Architecture: i386
Date: Sat Jul 25 17:44:55 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/audacious2
Package: audacious 2.1-1ubuntu1
ProcCmdline: audacious2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0xab6020 <SAD_dither_process_buffer+32>: mov 0x18(%eax),%eax
 PC (0x00ab6020) ok
 source "0x18(%eax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: audacious
StacktraceTop:
 SAD_dither_process_buffer () from /usr/lib/libSAD.so.2
 ?? ()
 write_output () from /usr/lib/audacious/Input/madplug.so
 decode_loop () from /usr/lib/audacious/Input/madplug.so
 ?? () from /usr/lib/audacious/Input/madplug.so
Title: audacious2 crashed with SIGSEGV in SAD_dither_process_buffer()
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Benjamin Drung (bdrung)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test Audacious 2.3 from the latest stable Ubuntu version (10.04) or the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect #404586, and any other logs that are relevant for this particular issue.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Benjamin Drung (bdrung)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from Jörn Horstmann. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.