https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #9 from Ovear <ove...@gmail.com> ---
Hi,
I have done some tests of this situation.
> I think I'd stepwise reduce the MemoryHigh value rather than removing the
> override.
Thanks for your suggestion, and you predicted exactly what will happen next.
First, the good news: baloo works with the updated version. It can initialize,
load the index and is operational for both indexing and searching.
```
$ LANG=en_US.UTF8 balooctl6 status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 700,557
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 12.17 GiB
● kde-baloo.service - Baloo File Indexer Daemon
Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset:
enabled)
Drop-In: /home/REDACTED/.config/system/user/kde-baloo.service.d
└─override.conf
Active: active (running) since Wed 2024-07-10 18:20:26 CST; 50s ago
Process: 1441235 ExecCondition=/usr/bin/kde-systemd-start-condition
--condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited,
status=0/SUCCESS)
Main PID: 1441238 (baloo_file)
Tasks: 3 (limit: 76867)
Memory: 222.6M (high: 512.0M available: 289.3M peak: 223.5M)
CPU: 20.640s
CGroup:
/user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
└─1441238 /usr/lib/kf6/baloo_file
```
However, there's also some bad news. About a day after I reverted my changes to
systemd service files, baloo got stuck again.
The `balooctl6 status` hung up and didn't response.
Upon a quick diagnosis, I found that baloo hit the memory limit again.
```
$ balooctl6 -v
baloo 6.2.0
$ ps -e -o pid,comm,pmem,rss|grep baloo
45489 baloorunner 0.5 363196
1144015 baloo_file 1.5 984736
1322906 baloo_file_extr 1.4 922908
$ systemctl status --user kde-baloo.service
● kde-baloo.service - Baloo File Indexer Daemon
Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset:
enabled)
Active: active (running) since Mon 2024-07-08 02:47:52 CST; 2 days ago
Process: 1144013 ExecCondition=/usr/bin/kde-systemd-start-condition
--condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited,
status=0/SUCCESS)
Main PID: 1144015 (baloo_file)
Tasks: 5 (limit: 76867)
Memory: 584.4M (high: 512.0M available: 0B peak: 584.9M)
CPU: 3min 49.366s
CGroup:
/user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
├─1144015 /usr/lib/kf6/baloo_file
└─1322906 /usr/lib/kf6/baloo_file_extractor
```
After changeing MemoryHigh to 50%, baloo quickly consumed 3GB of memory and
went back to operation.
```
Memory: 1.3G (high: 31.2G available: 5.7G peak: 3.0G)
```
I assumed this might be due to baloo indexing some files that require more
memory. I am trying to isolate and reproduce this issue and will update once I
make progress.
PS: I have tried creating small text files, and baloo works with the default
MemoryHigh settings currently. Any advice or hints to isolate this problem
would be greatly welcomed.
--
You are receiving this mail because:
You are watching all bug changes.
