https://bugs.kde.org/show_bug.cgi?id=367480
--- Comment #77 from Bob Miller <rmiller...@gmail.com> --- Created attachment 114688 --> https://bugs.kde.org/attachment.cgi?id=114688&action=edit New crash information added by DrKonqi baloo_file_extractor (5.48.0) using Qt 5.9.6 - What I was doing when the application crashed: 1. Something causes Baloo to crash (do not know what). I was reading kmail in this instance. 2. Logout, then login again 3, User is presented with the "baloo crashed -- restart?" graphic. 4. If restart is selected, baloo quckly consumes 100% CPU 5. Killing the process, logging out and logging back in again does not solve the problem. User is always presented with item #3 above. My guess is that index is corrupted and no amount of restarts solves the problem. Workaround: Go to ~/.local/share/baloo Remove files from baloo directory Logout, login. Baloo will remake the index, then be OK until the next crash. -- Backtrace (Reduced): #6 0x00007efd41d60770 in Baloo::PositionCodec::decode(QByteArray const&) () from /lib64/libKF5BalooEngine.so.5 #7 0x00007efd41d50ce4 in Baloo::PositionDB::get(QByteArray const&) () from /lib64/libKF5BalooEngine.so.5 #8 0x00007efd41d5eb34 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5 #9 0x00007efd41d57c62 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5 #10 0x000055e379ff8e2c in Baloo::App::processNextFile() () -- You are receiving this mail because: You are watching all bug changes.
