Bug 127561 - crashing after play. Mood Analyzer?
Summary: crashing after play. Mood Analyzer?
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-18 12:05 UTC by Josh Goodwin
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Goodwin 2006-05-18 12:05:35 UTC
Version:           1.4.0 (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
Compiler:          4.0.3 
OS:                Linux

I just upgraded to 1.4.0 and couldn't wait to try the mood analyzer. That is enabled. Now whenever I play a song, amarok crashes a few seconds into it. This happens on the handful of mp3's I've tried. Sure enough, if I disable use moods, the issue goes away. This backtrace seems to confirm it:

*** WARNING: Recoverable frame level error in file /mnt/store/music/Full Studio Discography's/Disturbed - Discography/(2000) The Sickness/Disturbed - Voices.mp3 (lost synchronization)
amarok:     MakeMood: Done processing. Stoping...[Thread 1149282656 (LWP 23595) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1333922144 (LWP 23618)]
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00002aaab2b3c6f8 in ?? ()
#2  0x0000000000000000 in ?? ()


(gdb) ni
amarok:     [CollectionDB] sqlite3_step: BUSY counter: 1
amarok:     BEGIN: ScanController::ScanController(CollectionDB*, bool, const QStringList&)
amarok:       BEGIN: void ScanController::initIncremental()
amarok:       END__: void ScanController::initIncremental() - Took 0.67s
amarok:     END__: ScanController::ScanController(CollectionDB*, bool, const QStringList&) - Took 0.67s
amarok:   END__: virtual void ThreadWeaver::Thread::run() - Took 1.4e+02s
amaroK::Crash::crashHandler ()



Also there is the email that Amarok wanted to send (email was down..)


======== DEBUG INFORMATION  =======
Version:    1.4.0
Engine:     xine-engine
Build date: May 17 2006
CC version: 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
KDElibs:    3.5.2
TagLib:     1.4.0

==== file /usr/lib/amarok/amarokapp =======
/usr/lib/amarok/amarokapp: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux 2.6.0, not stripped


==== (gdb) bt =====================
Using host libthread_db library "/lib/libthread_db.so.1".
==== (gdb) thread apply all bt ====


==== kdBacktrace() ================
[
0: /usr/lib/libkdecore.so.4(_Z11kdBacktracei+0x46) [0x38c42366f6]
1: /usr/lib/libkdecore.so.4(_Z11kdBacktracev+0xe) [0x38c42369ae]
2: amarok(_ZN6amaroK5Crash12crashHandlerEi+0x80f) [0x40728f]
3: /lib/libc.so.6 [0x38bf82f1b0]
]


Other than this 1.4.0 seems like a good release. I can't wait to start using moods though (=. Thanks to the Amarok team, and if I can help provide information please ask.
Comment 1 Roberto 2006-05-21 21:17:11 UTC
The same here in amarok 1.4, Debian SID amd64.
Comment 2 Adeodato Simó 2006-05-27 15:40:00 UTC
I have another couple reports against the Debian package, both from amd64 users.
Comment 3 Mark Kretschmann 2006-05-31 12:09:01 UTC
Moodbar is removed in 1.4.1, so this report becomes invalid. For now, just disable moodbar.