https://bugs.kde.org/show_bug.cgi?id=386513
--- Comment #10 from Harald Sitter <sit...@kde.org> --- At least the bookmarks runner does eventually cap out (for repeated krun queries anyway). What appears to happen is that every thread gets its own sql connection and they each have about a 1-2 MiB heap. Terribly inefficient and particularly troublesome with the huge amount of runner threads we can have these days. These appear to also not get shut down again. So mem consumption doesn't go down once krunner is idle again :S -- You are receiving this mail because: You are watching all bug changes.
