SUMMARY Im on latest version of linux kernel, OS packages (including kde related) Since some time ago, baloo_file_extractor once the pc is started, start eating all the RAM until the pc locks (because no available RAM) and I have to force a restart. The only way to stop it is to remember that each time I start the pc, I have to kill all the baloo related processes. STEPS TO REPRODUCE 1. Start the PC 2. Wait some few minutes until baloo_file_extractor gets all the RAM and the PC gets locked and freeze. OBSERVED RESULT PC gets locked after a while EXPECTED RESULT baloo should do its job without jeopardize the pc integrity SOFTWARE/OS VERSIONS Linux/KDE Plasma: kernel 4.19.2 (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION
I have 16 GB of RAM, baloo eats it all.
I've got the same poblem, also on Manjaro. After last updates it started eating a lot of ram and cpu usage. I used the baloo monitoring GUI and noticed it was stuck on a big folder, and also generating errors for every file. Solution was stop baloo, delete index, blacklist that big folder I have (with lots of git repos), and then start baloo again. Only blacklisting the huge folder and/or restarting didn't do it, I think the index got corrupted somehow.
Its not happening anymore, but probably not because the bug was somehow fixed, maybe it finished the cache process on whatever the folder that was causing trouble. I also have git folders on my documents. Anyway, why is the baloo file allowed to take more than 25% of the available ram? that has to be limited somehow. To take all the ram is unnaceptable in any circunstance.
(In reply to eduardo from comment #3) > Anyway, why is the baloo file allowed to take more than 25% of the available > ram? that has to be limited somehow. To take all the ram is unnaceptable in > any circunstance. Agree, same for CPU. It should only use that much CPU if pc is idle.
*** This bug has been marked as a duplicate of bug 400704 ***