amarok crashed with SIGSEGV in ThreadWeaver::Job::execute()

Bug #441853 reported by Steve McGrath
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Amarok
Invalid
High
amarok (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: amarok

Amarok crashes every time I try to activate dynamic mode. Once it does this, it will crash on startup every time, until I remove it's configuration from ~/.kde.

I haven't been able to make Amarok work since the first 2.2 beta version (2.1.85?) hit the Karmic repos.

I previously filed another bug about this, but this is the first time I could get apport to catch & report the crash.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: fab15882f8a3c1c4dd38353fc3ac84c0
CheckboxSystem: c4db302c6990d0bb1b00c5c328683b3b
Date: Sat Oct 3 18:57:39 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
Package: amarok 2:2.1.90-0ubuntu1
ProcCmdline: amarok -d --nofork
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0xb8ae35: mov (%esi),%eax
 PC (0x00b8ae35) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: amarok
StacktraceTop:
 ?? () from /usr/lib/libamaroklib.so.1
 ?? () from /usr/lib/libamaroklib.so.1
 ?? () from /usr/lib/libamaroklib.so.1
 ?? () from /usr/lib/libthreadweaver.so.4
 ThreadWeaver::Job::execute(ThreadWeaver::Thread*) ()
Title: amarok crashed with SIGSEGV in ThreadWeaver::Job::execute()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse pulse-access sambashare

Revision history for this message
Steve McGrath (smcgrath23) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:Dynamic::BiasSolver::ga_optimize (this=0x9c57c30,
QAlgorithmsPrivate::qSortHelper<QList<Dynamic::TrackListEnergyPair>::iterator, Dynamic::TrackListEnergyPair, qLess<Dynamic::TrackListEnergyPair> > (start=warning: (Internal error: pc 0xb8c300 in read in psymtab, but not in symtab.)
__static_initialization_and_destruction_0 ()
ThreadWeaver::JobRunHelper::runTheJob (this=0xac4fe26c,
ThreadWeaver::Job::execute (this=0x9c57c30, th=0x9c50fe8)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in amarok (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still an issue in 9.10 final?

Changed in amarok (Ubuntu):
importance: Medium → Undecided
status: New → Incomplete
Revision history for this message
Steve McGrath (smcgrath23) wrote :

Indeed. Dynamic mode causes Amarok to crash in the following circumstances:

1) Empty Playlist. Enabling dynamic mode crashes Amarok while generating the playlist.
2) Exisiting Playlist. Enabling dynamic mode and clicking "Re-populate" crashes Amarok while generating the playlist.
3) Existing Playlist, already playing. After enabling dynamic mode, Amarok crashes when skipping to the next track, as it attempts to select a new dynamic track for the playlist.

Changed in amarok (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Low
Changed in amarok:
status: Unknown → Invalid
Revision history for this message
Mackenzie Morgan (maco.m) wrote :

Fixed in 2.2.2 in Lucid

Changed in amarok (Ubuntu):
status: Triaged → Fix Released
Changed in amarok:
status: Invalid → Unknown
Changed in amarok:
importance: Unknown → High
status: Unknown → Invalid
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.