Summary: | Full Collection scan makes Amarok crash [malloc_consolidate, _int_malloc, my_malloc] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | hyper_ch <bugs.kde.org3> |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | mitchell, prasmal |
Priority: | NOR | ||
Version: | 2.3-GIT | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
hyper_ch
2009-12-28 18:03:10 UTC
seems to be something mysql related Please see the request at the bottom of the other bug (that this is now a dupe of). *** This bug has been marked as a duplicate of bug 220532 *** Created attachment 51736 [details]
New crash information added by DrKonqi
after an upgrade Amarok would not start. usunolem uninstalled and all configuration files amarok. Now when I plug the portable drive and then try to unmount it from Amarok, this program exits.
Prasmal, please do not comment on duplicate bugs, but on the original one. Also, your backtrace lacks debugging symbols: Thread 11 (Thread 0xab807b70 (LWP 4296)): [KCrash Handler] #6 malloc_consolidate (av=<value optimized out>) at malloc.c:5139 #7 0xb595d7ed in _int_malloc (av=<value optimized out>, bytes=<value optimized out>) at malloc.c:4373 #8 0xb595fd71 in *__GI___libc_malloc (bytes=3052571764) at malloc.c:3668 #9 0xb665660d in qMalloc (size=3052571764) at global/qmalloc.cpp:55 #10 0xb667be61 in QListData::detach3 (this=0xab806f40) at tools/qlist.cpp:137 #11 0xaa7f1a87 in ?? () from /usr/lib/kde4/amarok_collection-umscollection.so #12 0xaa7ed4eb in ?? () from /usr/lib/kde4/amarok_collection-umscollection.so #13 0xaa7ef032 in ?? () from /usr/lib/kde4/amarok_collection-umscollection.so #14 0xaa7f2da7 in ?? () from /usr/lib/kde4/amarok_collection-umscollection.so ... Please install debugging symbols and try reproducing the bug. It would be best to open a separate bug instead of commenting on a closed one. Also please paste the backtrace inline to make it searchable. Also Prasmal's bug doesn't look like the same thing as the original that this bug is a dup of. Prasmal, please open a new bug (and get debugging symbols). Dnia piątek 17 wrzesień 2010 o 11:58:13 Myriam Schweingruber napisał(a): > https://bugs.kde.org/show_bug.cgi?id=220422 > > > > > > --- Comment #4 from Myriam Schweingruber <myriam kde org> 2010-09-17 > 11:58:10 --- Prasmal, please do not comment on duplicate bugs, but on the > original one. Also, your backtrace lacks debugging symbols: > > Thread 11 (Thread 0xab807b70 (LWP 4296)): > [KCrash Handler] > #6 malloc_consolidate (av=<value optimized out>) at malloc.c:5139 > #7 0xb595d7ed in _int_malloc (av=<value optimized out>, bytes=<value > optimized out>) at malloc.c:4373 > #8 0xb595fd71 in *__GI___libc_malloc (bytes=3052571764) at malloc.c:3668 > #9 0xb665660d in qMalloc (size=3052571764) at global/qmalloc.cpp:55 > #10 0xb667be61 in QListData::detach3 (this=0xab806f40) at > tools/qlist.cpp:137 #11 0xaa7f1a87 in ?? () from > /usr/lib/kde4/amarok_collection-umscollection.so #12 0xaa7ed4eb in ?? () > from /usr/lib/kde4/amarok_collection-umscollection.so #13 0xaa7ef032 in ?? > () from /usr/lib/kde4/amarok_collection-umscollection.so #14 0xaa7f2da7 in > ?? () from /usr/lib/kde4/amarok_collection-umscollection.so ... > > Please install debugging symbols and try reproducing the bug. It would be > best to open a separate bug instead of commenting on a closed one. Also > please paste the backtrace inline to make it searchable. Hi. I didn't know which packet I need to install for debugging symbols. In debian based systems you need amarok-dbg, phonon-dbg, kdelibs5-dbg, libqt4-dbg and libglib2.0-0-dbg. See also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports |