237482 2010-05-13 12:29:53 +0000 Selecting multiple files causes crash 2010-05-13 19:26:32 +0000 1 1 2 Applications dolphin general 16.12.2 Ubuntu Linux RESOLVED DUPLICATE 236868 NOR crash --- 0 gav.creevy peter.penz19 frank78ac 0 oldest_to_newest 961401 0 gav.creevy 2010-05-13 12:29:53 +0000 Application: dolphin (1.4) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic-pae i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Shift selecting multiple files in Dolphin, not many (approx 20) seems to cause issues, looks like this has already been reported a few times (see possible duplicates). My coding knowledge is a bit rusty but it seems related to multiple threads requesting memory. The crash can be reproduced some of the time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [Current thread is 1 (Thread 0xb5175710 (LWP 19912))] Thread 3 (Thread 0xb101fb70 (LWP 20065)): [KCrash Handler] #6 0xb7811430 in __kernel_vsyscall () #7 0xb5b75651 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb5b78a82 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb5bac49d in ?? () from /lib/tls/i686/cmov/libc.so.6 #10 0xb5bb6591 in ?? () from /lib/tls/i686/cmov/libc.so.6 #11 0xb5bb69ea in ?? () from /lib/tls/i686/cmov/libc.so.6 #12 0xb5bb8afd in ?? () from /lib/tls/i686/cmov/libc.so.6 #13 0xb5bbaf9c in malloc () from /lib/tls/i686/cmov/libc.so.6 #14 0xb5e37b8d in qMalloc (size=1044) at global/qmalloc.cpp:55 #15 0xb5e3fb66 in QByteArray (this=0xb101e440, size=0, ch=0 '\000') at tools/qbytearray.cpp:1313 #16 0xb5e34749 in qt_error_string (errorCode=22) at global/qglobal.cpp:2125 #17 0xb5e3c5ff in report_error (code=0, where=0xb5fa866b "QMutex::lock", what=0xb5fa8649 "mutex lock") at thread/qmutex_unix.cpp:61 #18 0xb5e3c780 in QMutexPrivate::wait (this=0xb0700048, timeout=-1) at thread/qmutex_unix.cpp:80 #19 0xb5e38052 in QMutex::lock (this=0xb0717530) at thread/qmutex.cpp:167 #20 0xb5880000 in ?? () from /usr/lib/libsopranoclient.so.1 #21 0xb757ea30 in Nepomuk::MainModel::executeQuery (this=0x99f0280, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../../nepomuk/core/nepomukmainmodel.cpp:213 #22 0xb74ac3cd in Soprano::FilterModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsoprano.so.4 #23 0xb7572335 in Nepomuk::ResourceData::determineUri (this=0xb0705c60) at ../../../nepomuk/core/resourcedata.cpp:671 #24 0xb75736a0 in Nepomuk::ResourceData::load (this=0xb0705c60) at ../../../nepomuk/core/resourcedata.cpp:414 #25 0xb757419b in Nepomuk::ResourceData::property (this=0xb0705c60, uri=...) at ../../../nepomuk/core/resourcedata.cpp:271 #26 0xb7591cb7 in Nepomuk::Resource::property (this=0xb101f294, uri=...) at ../../../nepomuk/core/resource.cpp:280 #27 0xb7594d41 in Nepomuk::Resource::rating (this=0xb101f294) at ../../../nepomuk/core/resource.cpp:800 #28 0x080aa1e9 in KLoadMetaDataThread::run (this=0xa068b80) at ../../../../apps/dolphin/src/panels/information/kloadmetadatathread.cpp:95 #29 0xb5e3d32e in QThreadPrivate::start (arg=0xa068b80) at thread/qthread_unix.cpp:248 #30 0xb565396e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #31 0xb5c18a0e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xb1820b70 (LWP 20067)): #0 0xb7811430 in __kernel_vsyscall () #1 0xb5c25cf3 in ?? () from /lib/tls/i686/cmov/libc.so.6 #2 0xb5bbc697 in ?? () from /lib/tls/i686/cmov/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0xb5175710 (LWP 19912)): #0 0xb7811430 in __kernel_vsyscall () #1 0xb5c25cf3 in ?? () from /lib/tls/i686/cmov/libc.so.6 #2 0xb5bbc697 in ?? () from /lib/tls/i686/cmov/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) This bug may be a duplicate of or related to bug 236868, bug 236891. Possible duplicates by query: bug 236891. Reported using DrKonqi 961563 1 frank78ac 2010-05-13 19:26:32 +0000 Thanks for the bug report! This looks similar to a crash that has been reported already. *** This bug has been marked as a duplicate of bug 236868 ***