https://bugs.kde.org/show_bug.cgi?id=470382
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
Can you perhaps check whether baloo is being throttled by its systemd service
settings? There has been a recent change to these.
Arch uses systemd, or at least Google thinks so, so try
systemctl status --user kde-baloo
and see if that comes up with anything strange. It should give you the config
file, likely:
/usr/lib/systemd/user/kde-baloo.service
Check this and you will probably see a recently added line:
MemoryHigh=512M
This limits the amount of memory that baloo can grab. It could be that this is
too tight, you'll see if you are up at the limit in the systemctl status (it
will give you "high" and "available" values for memory). You can try changing
the line to:
MemoryHigh=50%
and see if that makes any difference.
--
You are receiving this mail because:
You are watching all bug changes.
