https://bugs.kde.org/show_bug.cgi?id=489588
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to Andrea Ippolito from comment #3)
> ... As for the command you suggested, I don't see any memory stats reported
> ...
It's possible that you are running an older distro, the KF5 patch was here:
https://invent.kde.org/frameworks/baloo/-/merge_requests/124
in April 2023. The KF6 patch was earlier...
However you can add the memory caps yourself with a
$ systemctl --user edit kde-baloo
and make sure the override file contains:
[Service]
MemoryHigh=25%
You can adjust the value, I find 25% OK although in some situations I set it to
40%
A further option is to add:
MemorySwapMax=0
which forcefully prevents Baloo swapping (but then, if it hits the limit, it
will crash with an Out Of Memory).
I think if you have an older Distro (dependent on how old), you might have
missed a patch that fixes mimetype lookups reading too much of the file. This
is an "unreliable memory" as I'm not sure if I can find the patch/description
but earlier I think if you wanted to find out the mimetype of a file (that
depended on magic values within the file), all the file was read. That's
something that might explain you findings...
--
You are receiving this mail because:
You are watching all bug changes.
