https://bugs.kde.org/show_bug.cgi?id=514150
--- Comment #4 from [email protected] --- (In reply to Richard Day from comment #3) > ... you wouldn't consider baloo continuing to consume considerable CPU for at > least 10 minutes after being disabled a problem? ... This is with content indexing....the extractor process is given a batch of files to index, 40 files at a time. Previously, certainly, setting baloo to disabled meant that baloo finished that batch but didn't start another. That can be longer or shorter. I'd need to check the behaviour now as there have been some very recent changes to how baloo is started (making sure it is always run under systemd and the associated memory limits). It may be that that also improves the indexing closedown. You should be able to manually stop all the baloo processes immediately with a "$ systemctl stop --user kde-baloo" -- You are receiving this mail because: You are watching all bug changes.
