https://bugs.kde.org/show_bug.cgi?id=475919
--- Comment #1 from tagwer...@innerjoin.org ---
An addendum...
On systems running systemd, Baloo runs with a cap on the memory it can use,
see:
https://invent.kde.org/frameworks/baloo/-/merge_requests/124
Limiting the RAM to 512 Mbyte means that it loads the system less.
When restarting the indexing with "balooctl purge", Baloo is not limited and
you may see an impact on responsiveness. Restarting the system will restart the
indexing following the systemd unit limits...
Alternatively, kill the baloo_file process, purge the database and start the
service with systemctl:
pkill baloo_file
balooctl purge
systemctl --user start kde-baloo.service
--
You are receiving this mail because:
You are watching all bug changes.
