https://bugs.kde.org/show_bug.cgi?id=406868
--- Comment #8 from tagwer...@innerjoin.org --- (In reply to Bart Ribbers from comment #7) > ... if I let Baloo run and the CPU usage of the process is 100% constantly ... In this instance, apologies, I think the best option is to do a "balooctl purge". That is, delete the index and reindex from scratch. The MDB_BAD_TXN is a report from LMDB library and suggests a corruption of the index. It might be worth checking to see how big the index is (with "balooctl indexSize") and see whether it is "too large" (coming up to the size of your RAM or the "Out of Memory" trigger threshold). If the index has "ballooned" in size, baloo uses a lot of CPU when trying to add/remove entries from it. I think though the only practical option is to purge and reindex. -- You are receiving this mail because: You are watching all bug changes.
