https://bugs.kde.org/show_bug.cgi?id=470382
Ovear <ove...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #2 from Ovear <ove...@gmail.com> ---
Hi,
Oh, change MemoryHigh works for me. According to status output from systemd,
baloo just hits the memory limited by systemd.
> Memory: 600.6M (high: 512.0M available: 0B)
Is that possible to output a warning when baloo failed to request more memory
as both systemd and baloo keep silence when it happened?
Or may be adjust default memory limit is an option? I am not sure what is the
optimal minimal required memory to keep Baloo from freezing. 512M may be a bit
insufficient.
But I also noticed Baloo doesn't seem to release memory after indexed.
Except that, is possible to find what file / reason it wants to index that
caused those high memory demand.
> Memory: 8.1G (high: 31.2G available: 23.0G)
Anyway, Thanks for your help.
I will try to add this to Baloo's ArchWiki troubleshoot section.
To those who may be affected by this, here is the process to increase systemd
memory limit.
1. Use systemd edit function to override default limit
> # systemctl --user edit kde-baloo
2. You may modify the file to something like below.
```
### Anything between here and the comment below will become the contents of the
drop-in file
[Service]
MemoryHigh=50%
### Edits below this comment will be discarded
```
3. Restart kde-baloo, and it should work.
> # systemctl restart --user kde-baloo
--
You are receiving this mail because:
You are watching all bug changes.
