~> lsof |grep 1903 |grep .local/share/baloo/index|grep -v lock|wc -l 3201 krunner uses 726GiB of VIRT memory and 410MiB RES, according to ksysguard: 7ea67c000000-7ea7bc000000 r--s 5242880 KB(size) 8 KB(RSS) 0 KB 8 KB(shared clean) 0 KB 0 KB 0 KB 8 KB 0 KB 0 KB 0 KB 0 KB .../.local/share/baloo/index the file is actually 8KiB in size. after yet another use of krunner it is now up to 1.1TiB of virtual memory and ~4700 mappings of the index file. The baloo file indexing should be disabled on my system to the best of my knowledge all of baloo should be disabled. Reproducible: Always Steps to Reproduce: 1. use krunner Actual Results: huge virtual memory usage baloo-core-4.14.3-1.3.x86_64 libbaloowidgets4-4.14.3-1.4.x86_64 libbaloofiles4-4.14.3-1.3.x86_64 libbalooqueryparser4-4.14.3-1.3.x86_64 plasma5-workspace-5.4.1-1.1.x86_64
Could you please paste the output for - $ balooctl status
Ping?
Thanks for pinging me! the Bugzilla mails got to my GMail spam folder and I missed the last one =/ > $ balooclt status > If 'balooctl' is not a typo you can use command-not-found to lookup the package that contains it, like this: > cnf balooctl aka it is not installed because I removed it.
Created attachment 95585 [details] KSysGuard Full Details
Comment on attachment 95585 [details] KSysGuard Full Details I'm having the same problem after "$balooctl disable" and rebooting. It seems to happen consistently each time I boot up. Memory usage is ok initially, but increases over time. After 2 hours of system up time with light KRunner usage, KRunner uses >1GB of memory. $balooctl status returns: Baloo is currently disabled. To enable, please run "balooctl enable" The full details from KSysGuard are attached. Some output from top: $ top -o RES top - 17:54:52 up 1:50, 1 user, load average: 0.43, 0.46, 0.44 Tasks: 180 total, 1 running, 179 sleeping, 0 stopped, 0 zombie %Cpu(s): 2.9 us, 1.1 sy, 0.0 ni, 96.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 5904828 total, 2663352 free, 2076380 used, 1165096 buff/cache KiB Swap: 2104316 total, 2104316 free, 0 used. 3634880 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2038 *** 20 0 1.594t 1.121g 95504 S 0.000 19.90 0:20.22 krunner
I'm having the same problem on ArchLinux even after a very short session. I'm also having plasma crashes, which may or may not be related. VIRT RES %CPU %MEM TIME+ S COMMAND 0.149t 171.9m 0.0 1.1 0:03.01 S krunner $ lsof |grep " 644 "|wc -l 8680 $ balooctl status Baloo is currently disabled. To enable, please run "balooctl enable" plasma-workspace 5.4.3-1 baloo 5.16.0-1 baloo-widgets 15.08.3-1 baloo4-akonadi 4.14.3-2 libbaloo4 4.14.3-2
It seems like this has been fixed in a recent update to openSUSE Tumbleweed, so the bug can be closed. Version info: openSUSE Tumbleweed 20160101 KDE Plasma 5.5.1 baloo-core 4.14.3-2.1 baloo5-tools 5.17.0-1.1
Created attachment 96743 [details] top with bloated krunner and plasmashell
My system was *kinda* slow when I got back to it today. See attachment (krunner used 0.31TiB virt and plasmashell 55GiB.) This is with a freshly updated Debian testing, plasma-workspace 4:5.4.3-1.
The same for me. kde-5.8.1 plasmashell takes 261G of virtual memory. maps file says almost everything is mapped to /home/rion/.local/share/baloo/index
Same for me. Kubuntu 16.04.1 with plasma-desktop 5.8.5-0ubuntu1~ubuntu16.04~ppa1 $ env LANG=C pmap -x -p `pidof plasmashell` | sort -n -k2| tail -5 00007f870348d000 65540 40 32 rw-s- /dev/shm/pulse-shm-1383956959 00007f8714a4e000 65540 4 4 rw-s- /dev/shm/pulse-shm-2802166547 00000000025fb000 262184 240276 238372 rw--- [ anon ] 00007f8724000000 2097152 2048 2048 rwx-- [ anon ] 00007f46ac000000 268435456 2152 0 r--s- /home/andrey/.local/share/baloo/index VSZ for baloo/index is 256GiB, while baloo is disabled $ env LANG=C balooctl status Baloo is currently disabled. To enable, please run "balooctl enable"
another 'me too'.. Fedora 25, plasma 5.8.5, krunner using 257 G of memory. balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 7 / 7 files Current size of index is 136.00 KiB
I have the same issue too, though it doesn't seem to causing any problems. I'm on Kubuntu 17.04, Plasma 5.9.5, krunner uses 256G virtual memory. ➜ balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 48024 / 48024 files Current size of index is 378,46 MiB
Yep, fixed with newer versions.