https://bugs.kde.org/show_bug.cgi?id=502641
--- Comment #15 from Niklāvs Koļesņikovs <[email protected]> --- The solution is as simple as MemoryHigh=10% . Also consider, if it would make sense to maybe just have a hard kill via MemoryMax=10% instead, since I really do not see the point of slowing a daemon down to an utter crawl. Ultimately those systemd limits are safeguards against bugs or other misbehavior and to me they don't seem like a good primary line of resource control, which should be handled by the daemon itself. -- You are receiving this mail because: You are watching all bug changes.
