Bug 339902

Summary:	Memory leak in krunner
Product:	[Plasma] krunner	Reporter:	Kai Uwe Broulik <kde>
Component:	general	Assignee:	Vishesh Handa <me>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bshah, lukas, simonandric5
Priority:	NOR
Version First Reported In:	5.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	valgrind log valgrind log 2

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?