| Summary: | Baloo uses all memory and swap | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Adam <adamvnz> |
| Component: | Baloo File Daemon | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | hessi88, stefan.bruens |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Htop view of memory usage | ||
I have the same issue on kde neon but without using nextcloud. After some time, baloo_file_extractor consumes most of the memory and swap. Also it utilizes one CPU core and whole user interface hangs sometimes for some seconds. When I kill the baloo_file_extractor, everything is fine again. *** This bug has been marked as a duplicate of bug 378754 *** |
Created attachment 107553 [details] Htop view of memory usage Hi I am using arch based linux. I am having issue with baloo consuming all memory and swap. After I have done a clean install and installed nextcloud dektop client all is ok. After I start nextcloud (can be days latter) baloo goes all out and uses all memory. If I uninstall nextcloud baloo continues to drain all memory. I have tried this on a couple of Arch based distros "Krevenge and Antergos" with the same result. Not sure if this is baloo's or nextclouds fault. Only solution I have at the moment is to add Indexing-Enabled=false to baloofilerc file Have tried stopping and starting baloo with no result