Every time I start the computer and login baloo_file starts to take up all my memory and then swap 16gb in total. Until the memory fills the cpu is at 100% after that it drops down but the memory and swap usage from baloo_file don't seam to ever go down. This kills performance making it almost impossible to do anything if I don't kill baloo_file first.
so I restarted my computer again and it is still doing this.
just logging out and then in triggers it.
Could you please run baloo under massif and provide us with a massif file? This will give us information about the part of Baloo which is consuming a lot of memory. 1. Install debug symbols for Baloo (and Qt if possible) 2. pkill baloo_file 3. valgrind --tool=massif baloo_file
Git commit 9b17d81b5152d28eba80b4b67fbda2ca5da41054 by Vishesh Handa. Committed on 14/12/2015 at 23:09. Pushed by vhanda into branch 'master'. SearchStore: Gracefully handle empty term values This happens on calling the baloosearch executable with an empty string or a few spaces. FIXED-IN: 5.18 M +3 -0 src/lib/searchstore.cpp http://commits.kde.org/baloo/9b17d81b5152d28eba80b4b67fbda2ca5da41054
The commit doesn't fix the bug. I pasted the wrong bug number.
I can no long do anything related to this bug I have moved to a manjaro based gnome system after a simple apt-get upgrade killed sddm and kde to a unrecoverable state.
*** This bug has been marked as a duplicate of bug 359119 ***