https://bugs.kde.org/show_bug.cgi?id=500665
Oded Arbel <o...@geek.co.il> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |o...@geek.co.il
--- Comment #56 from Oded Arbel <o...@geek.co.il> ---
I think I have the same issue - baloo_file takes ~300M of RAM and ~50% of a
CPU, and htop shows it in D status all the time, while balooctrl6 monitor says
"Idle (Powersave)" and shows no traffic.
After restart of the systemd kde-baloo.service user service, the problem has
disappeared (for now). I'll add more info when it happens again.
The kde-baloo.service on my system (Neon) has a limit of 512MB, which seems
quite high to me - that's a significant chunk of memory for a background
service that is supposed to be idle most of the time.
Operating System: KDE neon 6.3
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.3
Kernel Version: 6.11.0-21-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 31.0 GiB of RAM
Graphics Processor: Intel® Graphics
--
You are receiving this mail because:
You are watching all bug changes.
