Hi Alexander, On Sun, Jan 6, 2013 at 9:22 AM, Alexander Puchmayr <alexander.puchm...@linznet.at> wrote: > Hi there, > > After the upgrade from Amarok 2.5 to 2.6, it crashes after a random amount of > time after starting the application. Sometimes it crashes in less than a > minute, sometime I can even play a whole album. > > I've added the output of "amarok --debug" for analysis. The picture looks > different each time, some times (but not every time) I get the message > > *** glibc detected *** amarok: malloc(): memory corruption (fast): > 0x0000000002c85240 *** > > Another common thing is that the last line I see in the debug-output has to do > something with ScanManager::checkForDirectoryChanges.
Thank you for the debug output, but what we would need is a backtrace. Please do the following: (install the package gdb if you not already have it) gdb amarok run -d --nofork when it crashes, type thread apply all bt and only give us that part after that line Also some more information about your distribution and KDE version would be helpful. Regards, Myriam -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) _______________________________________________ Amarok mailing list Amarok@kde.org https://mail.kde.org/mailman/listinfo/amarok
