Have also a crashing baloo: https://bugs.kde.org/show_bug.cgi?id=390363 -- On Mittwoch, 14. Februar 2018 11:23:45 CET Mykola Krachkovsky wrote:

Hi,

baloo_file started to crash several snapshots ago. First Plasma 5.12 Beta (aka 5.11.95) snapshot was ok. But some time after that crashes started, not sure exactly when. Crash happens after some changes in files (e.g., new file) or if balooctl check started.

Should I report this upstream, open bugzilla report or recreate baloo db?

crash from drkonqi:

Thread 3 (Thread 0x7f1a6bdfe700 (LWP 12536)): [KCrash Handler] #6 0x00007f5a79110490 in __memmove_avx_unaligned_erms () from /lib64/libc.so. 6 #7 0x00007f5a79b00460 in QByteArray::QByteArray(char const*, int) () from / usr/lib64/libQt5Core.so.5 #8 0x00007f5a7a3dfca1 in Baloo::IdFilenameDB::get (this=this@entry=0x7f1a6bdfda00, docId=<optimized out>, docId@entry=73800478881744899) at /usr/src/debug/baloo5-5.42.0-1.1.x86_64/src/ engine/idfilenamedb.cpp:97 #9 0x00007f5a7a3d95da in Baloo::DocumentUrlDB::get (this=this@entry=0x7f1a6bdfda80, docId=docId@entry=73800478881744899) at /usr/ src/debug/baloo5-5.42.0-1.1.x86_64/src/engine/documenturldb.cpp:134 #10 0x00007f5a7a3e9fb4 in Baloo::Transaction::documentUrl (this=this@entry=0x7f1a6bdfdb30, id=id@entry=73800478881744899) at /usr/src/ debug/baloo5-5.42.0-1.1.x86_64/src/engine/transaction.cpp:104 #11 0x0000558a7afb639e in Baloo::UnindexedFileIndexer::run (this=0x558a7b415910) at /usr/src/debug/baloo5-5.42.0-1.1.x86_64/src/file/ unindexedfileindexer.cpp:64 #12 0x00007f5a79af9b82 in QThreadPoolThread::run() () from /usr/lib64/ libQt5Core.so.5 #13 0x00007f5a79afc930 in QThreadPrivate::start(void*) () from /usr/lib64/ libQt5Core.so.5 #14 0x00007f5a780fc558 in start_thread () from /lib64/libpthread.so.0 #15 0x00007f5a790ae72f in clone () from /lib64/libc.so.6

Am Mittwoch, 14. Februar 2018, 11:23:45 CET schrieb Mykola Krachkovsky:

baloo_file started to crash several snapshots ago. First Plasma 5.12 Beta (aka 5.11.95) snapshot was ok. But some time after that crashes started, not sure exactly when. Crash happens after some changes in files (e.g., new file) or if balooctl check started.

Should I report this upstream, open bugzilla report or recreate baloo db?

In my case ballo is not crashing, but apparently rebuilding the database (after update to 17.12.2) with the effect that the all processors are fully active..... Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org