Summary: | baloo_file_extractor eats the whole RAM | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | eduardo <edoantonioco> |
Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | grave | CC: | bmilreu, nate |
Priority: | NOR | ||
Version: | 5.52.0 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
eduardo
2018-11-21 15:18:21 UTC
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 *** |