Bug 339902 - Memory leak in krunner
Summary: Memory leak in krunner
Status: RESOLVED FIXED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Vishesh Handa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-12 12:10 UTC by Kai Uwe Broulik
Modified: 2015-02-18 15:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
valgrind log (15.00 KB, text/plain)
2014-10-30 14:49 UTC, Bhushan Shah 		Details
valgrind log 2 (15.00 KB, text/plain)
2014-10-30 14:51 UTC, Bhushan Shah 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2014-10-12 12:10:28 UTC 
At the moment, my KRunner uses about 1.6GiB of RAM and with every query I enter its memory consuption rises by 2 to 3 MiB (or up to 10 MiB depending on how many results there are / how generic the query is). This does not happen if I disable all the Baloo runners (Images, Audio, Documents, Folders, etc)

Reproducible: Always
Comment 1 Kai Uwe Broulik 2014-10-29 16:42:24 UTC 
Happens independently of whether Baloo is enabled or not
Comment 2 Bhushan Shah 2014-10-29 16:44:55 UTC 
I can confirm this..
Comment 3 Bhushan Shah 2014-10-30 14:49:46 UTC 
Created attachment 89381 [details]
valgrind log
Comment 4 Bhushan Shah 2014-10-30 14:51:21 UTC 
Created attachment 89382 [details]
valgrind log 2
Comment 5 Vishesh Handa 2015-02-03 14:33:17 UTC 
@Bhushan: You'll need to attach massif logs since it isn't actually a memory leak, rather someone hoarding a lot of memory.

@Kai: Are you still having this problem with Plasma 5.2?