https://bugs.kde.org/show_bug.cgi?id=502641
--- Comment #8 from [email protected] --- (In reply to Méven from comment #7) > Here is a stack trace as baloo_file was using 93% cpu hanging... Is it managing to process any files or just spinning its wheels? You might be able to tell with iotop... It's baloo_file rather than baloo_file_extractor so it's not stuck doing content indexing, baloo_file can get overloaded if you have a large index and then do a "big delete". If you've set up and then deleted a large folder tree, Baloo removes the indexed files one by one. That's hard... I think the recommendations above to check the memory use (it Baloo up against the systemd limit?) and grant it more work space (setting MemoryHigh=25% for example). I'm afraid dumpcracking is not one of my skills.... -- You are receiving this mail because: You are watching all bug changes.
