https://bugs.kde.org/show_bug.cgi?id=470665
--- Comment #7 from tagwer...@innerjoin.org ---
(In reply to Maximilian Böhm from comment #5)
> Memory: 512.0M (high: 512.0M available: 0B)
My suspicion is that the systemd service definition has capped the memory that
baloo can use. This looks very much like Bug 470382. There's a description of
what you can check here:
https://bugs.kde.org/show_bug.cgi?id=470382#c1
You can try:
systemctl --user edit kde-baloo
and change the
MemoryHigh=512M
to
MemoryHigh=50%
I'm not 100% certain here because...
> When did this start… I cannot say for certain. I have witnessed it for a
> longer time but mainly ignored it. Maybe even years? I’m just fed up with
> this situation as of today.
... you've had problems for a while, the 512 MByte limit is quite recent.
> Is there a command to show which file Baloo tries to index?
Yes, "balooctl monitor". However this shows you the files as baloo does its
second phase "content indexing". I suspect that the indexing *something* is the
first phase, when baloo is scanning the system looking to see what's new or
changed.
--
You are receiving this mail because:
You are watching all bug changes.
