KDE's Baloo file indexer using an extremely excessive amount of resources #41
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For instance, once I found that Baloo had created a 174 GB file index. It was compressed fortunately, so it wasn't actually that big. But still very big. Yesterday, I found 7341 Baloo core dumps taking up 4.1 GB of space. And today, it used 50% CPU for the half of the day. That's like using 12 of our 24 threads on full throttle. Terrible.
The workaround right now is to disable file indexing in the settings app.
I think I fixed it by deleting
~/.local/share/baloo
and purging the file index withbalooctl purge
. Baloo rebuilt the index and so far it looks good. Reopen this if you encounter a similar issue and this doesn't fix it.This has returned again. A
balooctl purge
seems to bring it back into control.Baloo has once again returned...
About once every week, it just goes crazy and I need to run
sudo killall baloo_file
to kill all the Baloo stuff. It also creates a gazillion coredumps again.This is an example of one of the coredumps:
I did a
balooctl purge
and that seemed to fix things so closing for now.