Summary: | Segmentation fault on startup [@ ServiceSqlRegistry::getTrack] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Marcus Harrison <marcus> |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ahepas1999, aleksandr_s85, amanic, carlos, david.lentini, exoool, gasgom, gdragonmtn, info, jbgibson1967, jiacontrerasp, kecskebak.blog, kfunk, loskutov, matej, mexicano_neuber, mstraf, netfalo+kdebugs, nhn, p92, ralf-engels, sndsergiu, thomas.defranc |
Priority: | NOR | Keywords: | regression, release_blocker |
Version: | 2.6.0 | ||
Target Milestone: | 2.7 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/amarok/897294f3c65834e555a6c28d5b36f65aad2ec54c | Version Fixed In: | 2.7 |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Marcus Harrison
2010-03-16 16:32:24 UTC
I'm unable to reproduce. Does this happen with all genres or just a specific one? It seems to happen most consistently on the, "Classical" genre - I expect it's something to do with the huge number of items there. Ok, I can reproduce it with the classic genre. The crash does not always happen, just sometimes... Next question: is it the number of items or maybe a specific item in there? Do you have a Magnatune membership? I was only able to reproduce on a machine with set up membership info. This is the backtrace from altest git master, looks a bit different than yours, might be due to code changes since 2.3.0: Thread 5 (Thread 0xa7ea9b70 (LWP 8386)): [KCrash Handler] #6 0xb6e42704 in ServiceSqlQueryMaker::handleResult (this=0xa2f6ba0, result=...) at /home/sven/git/krohlass-clone/src/services/ServiceSqlQueryMaker.cpp:578 #7 0xb6e4455a in ServiceSqlWorkerThread::run (this=0x9eb7fa8) at /home/sven/git/krohlass-clone/src/services/ServiceSqlQueryMaker.cpp:58 #8 0xb50ef558 in ThreadWeaver::JobRunHelper::runTheJob (this=0xa7ea923c, th=0xa9c00968, job=0x9eb7fa8) at /usr/src/debug/kdelibs-4.4.1/threadweaver/Weaver/Job.cpp:106 #9 0xb50ef6b3 in ThreadWeaver::Job::execute (this=0x9eb7fa8, th=0xa9c00968) at /usr/src/debug/kdelibs-4.4.1/threadweaver/Weaver/Job.cpp:135 #10 0xb50ebac2 in ThreadWeaver::ThreadRunHelper::run (this=0xa7ea92c4, parent=0x8c474b0, th=0xa9c00968) at /usr/src/debug/kdelibs-4.4.1/threadweaver/Weaver/Thread.cpp:95 #11 0xb50edc7a in ThreadWeaver::Thread::run (this=0xa9c00968) at /usr/src/debug/kdelibs-4.4.1/threadweaver/Weaver/Thread.cpp:142 #12 0xb66780bf in QThreadPrivate::start (arg=0xa9c00968) at thread/qthread_unix.cpp:248 #13 0xb56136e5 in start_thread () from /lib/libpthread.so.0 #14 0xb5613600 in ?? () from /lib/libpthread.so.0 No, I don't have Magnatune membership. I expect it's got more to do with the number of items, than a particular item causing it. I'm using it on a netbook and experienced some serious slowdowns when dragging the Classical genre over before it crashed. *** Bug 250684 has been marked as a duplicate of this bug. *** I come from the Bug 250684 [https://bugs.kde.org/show_bug.cgi?id=250684]. And I found the following message when I ran in debug mode, I think it has something to do with the database Created attachment 51847 [details]
New crash information added by DrKonqi
I can reproduce this error quite often when dragging whole magnatune genre to middle window(replace playlist). This happens more often if I do that quick after amarok start(while it's still loading some components)
Nusch, this report is about a version way ahead of yours. Also, your backtrace is not useful as you lack debugging symbols, see also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Please test with Amarok 2.3.2 and paste the backtrace in-line so it is searchable Myriam, Look at first post by Marcus Harrison - he's reporting problem with amarok 2.3.0 and that the same version I'm reporting. Maybe you meant another report. Report was generated with auto tool DrKonqi which rate if report is useful(in this case 3/3 stars)and asks for launching aptitude if debugging symbols are not available. Thats also the reason it's been added as attachement. The only unresolved symbols are related to alsa, pulse and xine what has nothing to do GUI and Qt libraries. The current version is in the bug header, and that is what matters. Please try again with the latest Amarok version, which is 2.3.2 I will file a bug for Dr. Konqi, it should not paste backtraces as attachements, it would really spare us triagers a lot of work. Actually, the Dr. Konqi problem with attaching backtraces is already solved in the newer version, see comment #1 in bug 244522 You should upgrade your KDE version, see http://kubuntu.org/news for more informations. Original reproduce steps work for me. Please re-try and re-open if it crashes for you. *** Bug 301014 has been marked as a duplicate of this bug. *** Reopening based on new reports. *** Bug 305345 has been marked as a duplicate of this bug. *** *** Bug 305348 has been marked as a duplicate of this bug. *** (In reply to comment #16) > *** Bug 305348 has been marked as a duplicate of this bug. *** Backtrace from that report: Thread 2 (Thread 0x7facd19e2700 (LWP 5571)): [KCrash Handler] #6 same_key (key0=..., h0=145098177, this=0x100000005) at /usr/include/QtCore/qhash.h:225 #7 QHash<QString, KSharedPtr<Meta::Track> >::findNode (this=0x2012dc8, akey=..., ahp=0x7facd19e193c) at /usr/include/QtCore/qhash.h:887 #8 0x00007face216c989 in QHash<QString, KSharedPtr<Meta::Track> >::insert (this=0x2012dc8, akey=..., avalue=...) at /usr/include/QtCore/qhash.h:759 #9 0x00007face2166df1 in SqlRegistry::getTrack (this=0x2012db0, path=<optimized out>) at /usr/src/debug/amarok-2.6.0/src/core-impl/collections/db/sql/SqlRegistry.cpp:173 #10 0x00007face214a9cb in Collections::SqlCollection::trackForUrl (this=0x1ffc990, url=...) at /usr/src/debug/amarok-2.6.0/src/core-impl/collections/db/sql/SqlCollection.cpp:423 #11 0x00007fad00439681 in CollectionManager::trackForUrl (this=<optimized out>, url=...) at /usr/src/debug/amarok-2.6.0/src/core-impl/collections/support/CollectionManager.cpp:457 #12 0x00007fad003dd45c in MetaProxy::Worker::run (this=0x63c0130) at /usr/src/debug/amarok-2.6.0/src/core-impl/meta/proxy/MetaProxyWorker.cpp:32 #13 0x000000304cc0c9fb in ThreadWeaver::JobRunHelper::runTheJob (this=0x7facd19e1ca0, th=0x2572480, job=0x63c0130) at /usr/src/debug/kdelibs-4.8.4/threadweaver/Weaver/Job.cpp:106 #14 0x000000304cc0cb6c in ThreadWeaver::Job::execute (this=0x63c0130, th=0x2572480) at /usr/src/debug/kdelibs-4.8.4/threadweaver/Weaver/Job.cpp:135 #15 0x000000304cc0c1bf in ThreadWeaver::ThreadRunHelper::run (this=0x7facd19e1d20, parent=0x222e100, th=0x2572480) at /usr/src/debug/kdelibs-4.8.4/threadweaver/Weaver/Thread.cpp:95 #16 0x000000304cc0c27b in ThreadWeaver::Thread::run (this=0x2572480) at /usr/src/debug/kdelibs-4.8.4/threadweaver/Weaver/Thread.cpp:142 #17 0x000000303607bbcb in QThreadPrivate::start (arg=0x2572480) at thread/qthread_unix.cpp:307 #18 0x000000302bc07d90 in start_thread (arg=0x7facd19e2700) at pthread_create.c:309 #19 0x000000302b4f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 *** Bug 306646 has been marked as a duplicate of this bug. *** *** Bug 307184 has been marked as a duplicate of this bug. *** *** Bug 307462 has been marked as a duplicate of this bug. *** Git commit 897294f3c65834e555a6c28d5b36f65aad2ec54c by Matěj Laitl. Committed on 02/10/2012 at 22:20. Pushed by laitl into branch 'master'. Fix thread safety of SqlRegistry Most notably the SqlRegistry::getTrack( const KUrl &url ) lacked the locking, which was a source of data race conditions. I also added locking to another method that was lacking it and cleaned up a bit QMutexLocker usage. FIXED-IN: 2.7 M +1 -0 ChangeLog M +18 -16 src/core-impl/collections/db/sql/SqlRegistry.cpp M +7 -7 src/core-impl/collections/db/sql/SqlRegistry.h http://commits.kde.org/amarok/897294f3c65834e555a6c28d5b36f65aad2ec54c *** Bug 308667 has been marked as a duplicate of this bug. *** *** Bug 308828 has been marked as a duplicate of this bug. *** *** Bug 308979 has been marked as a duplicate of this bug. *** *** Bug 310439 has been marked as a duplicate of this bug. *** *** Bug 310934 has been marked as a duplicate of this bug. *** *** Bug 311289 has been marked as a duplicate of this bug. *** This bug is marked as resolved fixed. Yet it happened to me today with the freshly updated Fedora 18 Beta. I'm sorry, but I'm a little puzzled as to what's going on. (In reply to comment #28) > This bug is marked as resolved fixed. Yet it happened to me today with the > freshly updated Fedora 18 Beta. > > I'm sorry, but I'm a little puzzled as to what's going on. See the version number for the fix: 2.7 You still use 2.6 AFAIK, 2.7 is not released yet. Ah, that makes sense now - I'm sorry I'm so stupid! Many thanks for your help. *** Bug 312147 has been marked as a duplicate of this bug. *** *** Bug 312241 has been marked as a duplicate of this bug. *** *** Bug 313064 has been marked as a duplicate of this bug. *** *** Bug 313169 has been marked as a duplicate of this bug. *** *** Bug 314163 has been marked as a duplicate of this bug. *** *** Bug 314364 has been marked as a duplicate of this bug. *** *** Bug 315270 has been marked as a duplicate of this bug. *** *** Bug 320913 has been marked as a duplicate of this bug. *** |