Hi Panzi, Can you please do two things:
1. start Amarok with "gdb --args amarok --debug --nofork" When amarok hangs you can "ctr-c" the debugger and get a stack trace. 2. Since you are saying "since a few days" it might be possible to find the offending commit. Can you try to find that? Maybe with "git bisect" Thanks, Ralf On Di, 2011-09-06 at 12:00 +0000, amarok-devel-requ...@kde.org wrote: > Date: Tue, 06 Sep 2011 04:42:11 +0200 > From: Mathias Panzenb?ck <grosser.meister.mo...@gmx.net> > To: Amarok Devel <amarok-devel@kde.org> > Subject: corrupted double-linked list > Message-ID: <4e658883.7030...@gmx.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Since a few days amarok does not shut down correctly anymore but gives > this message on quit and hangs: > > amarok: END__: virtual App::~App() [DELAY Took (quite long) 7.6s] > amarok: BEGIN: bool Dynamic::DynamicModel::savePlaylists(const > QString&) > amarok: END__: bool Dynamic::DynamicModel::savePlaylists(const > QString&) [Took: 0.065s] > amarok: BEGIN: virtual void Dynamic::BiasedPlaylist::requestAbort() > amarok: END__: virtual void Dynamic::BiasedPlaylist::requestAbort() > [Took: 0s] > amarok: BEGIN: virtual void Dynamic::BiasedPlaylist::requestAbort() > amarok: END__: virtual void Dynamic::BiasedPlaylist::requestAbort() > [Took: 0s] > amarok: BEGIN: virtual void Dynamic::BiasedPlaylist::requestAbort() > amarok: END__: virtual void Dynamic::BiasedPlaylist::requestAbort() > [Took: 0s] > amarok: BEGIN: virtual void Dynamic::BiasedPlaylist::requestAbort() > amarok: END__: virtual void Dynamic::BiasedPlaylist::requestAbort() > [Took: 0s] > amarok: [MySqlStorage] Deinitialized thread, count== 4 > *** glibc detected *** amarok: corrupted double-linked list: > 0x00000000010732a0 *** > > Then it can only be killed using -9. > > Say it if you want me to send you more information. > > -panzi _______________________________________________ Amarok-devel mailing list Amarok-devel@kde.org https://mail.kde.org/mailman/listinfo/amarok-devel
