https://bugs.kde.org/show_bug.cgi?id=332421
Martin Senftleben <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #45 from Martin Senftleben <[email protected]> --- I'm not sure if it's wise to add to this thread, but the topic is the same: for three days now baloo_file_extractor is, according to my ksysguard, the top RAM and particularly swap memory eater. The most peculiar, but maybe normal thing is, that it doesn't eat up all RAM (I have 16 GB installed, but bsysguard shows only 9 GB being used), but feeds on swap memory. The swap file is now at its limit (6.3/6.3 GB) and the machine is slowing down. I tried various commands mentioned here, all failed on my machine or produce no usable output: "ps aux | grep baloo_file_extractor" produces: "username 3076 43.5 49.3 272558692 8087596 ? DNl Okt24 3018:54 /usr/bin/baloo_file_extractor username 3575 0.0 0.0 10776 2016 pts/1 S+ 12:03 0:00 grep --color=tty -d skip baloo_file_extractor" and "sudo echo 3 > /proc/sys/vm/drop_caches" (in the hope that this might clear up space) produces: "Keine Berechtigung" (= no permission) Other things I didn't try. I run Manjaro Arch-Linux up-to-date, 64 bit. -- You are receiving this mail because: You are watching all bug changes.
