https://bugs.kde.org/show_bug.cgi?id=487916
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
I don't *think* there's anything specific about the big move to KF6 that would
trigger these sort of issues.
Maybe check a couple of things...
First, see how much memory Baloo is using. Nowadays, it is run via systemd by
default and constrained to 512 Mbyte RAM. Check whether this is actually
happening with
$ systemctl --user status kde-baloo
There are two possible concerns, one being it's been restarted and is *not*
running within this constraint.
The second, contrasting, possibility is that the index is very, very large (see
how big your ~/.local/share/baloo/index is) and Baloo is continuously reading,
dropping, rereading and redropping pages - trying to work within its 512 MB.
Both options *may* end up with high I/O - particularly if Baloo is starting to
swap.
--
You are receiving this mail because:
You are watching all bug changes.
