https://bugs.kde.org/show_bug.cgi?id=500665
Bug ID: 500665
Summary: Baloo File Extractor uses 25-40% CPU and 3 GB of RAM
while indexing an HDD and slows down the whole system
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.11.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: pos...@posteo.eu
Target Milestone: ---
Created attachment 178803
--> https://bugs.kde.org/attachment.cgi?id=178803&action=edit
Screenshot of htop
STEPS TO REPRODUCE
1. Have two a few TB HDDs with NTFS mounted under /media/foo/bar{1,2}
2. Add the mount points to the list of paths to be indexed
3. Index file names and file contents
4. Enable baloo
OBSERVED RESULT
baloo_runner starts baloo_file, which starts baloo_file_extractor
Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing files on
the HDD.
Worse it can actually slow down the whole system, making it lag and not fun to
work with. The issues are immediately gone when killing baloo_file_extractor.
`balooctl disable` does not directly stop the process but it takes a few
minutes.
Therefore I've disabled baloo with `balooctl disable` for now in general.
EXPECTED RESULT
Baloo File Extractor does never significantly slow down the system.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250222
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 31.2 GiB of RAM
lmdb: 0.9.30-2.3
System is installed on an NVMe using BTRFS
HDDs are two WD RED 7200 RPM with a few TB and NTFS
--
You are receiving this mail because:
You are watching all bug changes.
