Bug 384088 - Baloo uses all memory and swap
Summary: Baloo uses all memory and swap
Status: RESOLVED DUPLICATE of bug 378754
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-27 21:44 UTC by Adam
Modified: 2018-10-16 23:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Htop view of memory usage (259.02 KB, image/png)
2017-08-27 21:44 UTC, Adam 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Adam 2017-08-27 21:44:18 UTC 
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
Comment 1 Markus Heß 2017-09-18 10:18:45 UTC 
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.
Comment 2 Stefan Brüns 2018-10-16 23:51:33 UTC 

*** This bug has been marked as a duplicate of bug 378754 ***