https://bugs.kde.org/show_bug.cgi?id=386513
--- Comment #11 from Alexander Lohnau <alexander.loh...@gmx.de> --- >What appears to happen is that every thread gets its own sql connection and >they each have about a 1-2 MiB heap. I had the same suspicion. The thread usage is always problem when having a bit more complicated runners. A possible solution could be to use a D-Bus runner. This way we are on the safe side and could also use better caching and thus avoid making SQL queries when not needed. Especially since the runner could be loaded in the kickoff/kicker launcher and KRunner at the same time we could do a more agressive caching without keeping the same data in memory. Better caching could also be beneficial to reduce disk write operations(this has been extreme because of the combination of two bugs that have been fixed). And as you(@sitter) know we have big plans for the D-Bus runners, but the current state is already more than sufficient to port this runner. @davidedmundson What do you think about this? -- You are receiving this mail because: You are watching all bug changes.
