https://bugs.kde.org/show_bug.cgi?id=400704
--- Comment #54 from tagwer...@innerjoin.org ---
(In reply to postix from comment #53)
> Done, please see bug #500665
Referencing a discovery in that Bug
https://bugs.kde.org/show_bug.cgi?id=500665#c51
The issue was on a Tumbleweed system and this had "DefaultMemoryAllocation=no"
which prevented the "MemoryMax=512MB" limit in the unit file for Baloo working.
If Baloo, with a large index, is affecting performance on Tumbleweed (maybe
other SUSE systems?). Check that it is running under systemd with a "systemctl
status --user kde-baloo" and that the status includes a line reporting memory
usage.
--
You are receiving this mail because:
You are watching all bug changes.
