https://bugs.kde.org/show_bug.cgi?id=475707
Bug ID: 475707
Summary: `baloo_file` process taking up significant memory
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 5.103.0
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: drizzt...@gmail.com
Target Milestone: ---
SUMMARY
My current `baloo_file` process is taking up a report 6.1GB of memory, and
`balooctl status` is showing the size of the index is 8.8GB. The size of the
process seems excessively large to me.
This is from a fresh install a month ago of Debian 12.1, updated last week to
12.2. I also had an issue with `baloo_file_extrator` taking up >20GB of memory,
and spiking my SSD (Samsung 990 Pro) excessively, and causing issues because of
that. After adding some directory excludes, disabling scanning contents of
files (setting `contentIndexing` to `no`), doing a purge and restarting
indexing from scratch, and then taking a while and still having large amounts
of memory usage and SSD usage, it eventually completed it's initial indexing
and has seemed to settle down.
But now I notice `baloo_file` process is taking up a relatively large amount of
memory, which is obviously concerning. Despite having 96GB of memory, I run
some large VMs for work, and sometimes every bit of memory is needed.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 12.2 (kernel 6.1.0-13-amd64)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
ADDITIONAL INFORMATION
Ryzen 5800X3D
Radeon 7900XT
--
You are receiving this mail because:
You are watching all bug changes.
