FS#40222 - [kdebase-workspace] Huge memory usage/leak in krunner

Attached to Project: Arch Linux
Opened by Nicola Mori (snack) - Monday, 05 May 2014, 09:44 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 05 May 2014, 17:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
On my system krunner eats a lot of memory, eventually not releasing it and leading the system to instability. I can trigger this behavior by opening the launcher window in KDE by pressing Alt+F2 and writing a very simple math calculation, like "360/2=" or "180/3=" a few times. My memory monitoring plasmoid then shows a sharp peak and krunner results in using around 2GB of memory. OOM thread kill log from journalctl is attached.

Additional info:
* package version(s)
kdebase-workspace 4.11.9-2
kdelibs 4.13.0-1

* config and/or log files etc.
Log from journalctl of krunner OOM kill.

Steps to reproduce:
1) open launcher window with Alt+F2
2) type some simple math operations like "45*2=" or "36/3=" a few times
3) keep an eye on memory occupancy
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 05 May 2014, 17:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  baloo 4.13.0-2
Comment by Bogomil (smirky) - Monday, 05 May 2014, 11:01 GMT
Confirmed. I made about 6 or 7 calculations and the laptop froze. I had to switch to a different tty with a lot of patience and kill the X server which also took me a while :D. I think this should be reported upstream.
Comment by Andrea Scarpino (BaSh) - Monday, 05 May 2014, 12:14 GMT
Please report this upstream.
Comment by Nicola Mori (snack) - Monday, 05 May 2014, 14:03 GMT
It has been already reported:

https://bugs.kde.org/show_bug.cgi?id=332253

Sorry for reporting it also here.
Comment by Andrea Scarpino (BaSh) - Monday, 05 May 2014, 17:46 GMT
You did it right: reporting it here too made this patch to be applied to baloo 4.13.0-2

Loading...