https://bugs.kde.org/show_bug.cgi?id=449355
--- Comment #1 from tagwer...@innerjoin.org --- Sooo... Baloo has "seen" a load of files. That is baloo_file has picked up that you've copied loads to your Downloads folder, that doesn't take long in normal cases, and has queued them for content indexing You can watch to see what "content indexing" is happening if you run "balooctl monitor". You'll see files being indexed in batches of 40. It's possible that the baloo_file_extractor was choking on one particular file (think a multi-gigabyte mailbox file - but surprises come in all shapes, sizes and forms). During this work it'll be baloo_file_extractor taking the resources. if you've subsequently disabled indexing of ~/Downloads, baloo_file would see that it has to clean up all those records it had initially created (and the "content" for the 75% of the files you'd managed to index). That's hard work and can mean your index baloons in size, see Bug 437754. Can be the best solution, as opposed to waiting for 10's of thousands of records to be cleaned from the index, to purge and start again. I've seen that people in this situation, who have an SSD and a HDD, make sure that their .local/share/baloo folder is on the SSD to avoid all the "seek" work... -- You are receiving this mail because: You are watching all bug changes.
