https://bugs.kde.org/show_bug.cgi?id=498876
Bug ID: 498876
Summary: baloo_file_extractor uses a significant amount of
system resources; balooctl6 monitor simply shows ":
Ok"
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.10.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
The baloo_file_extractor process uses progressively larger amounts of memory
(currently ~700MiB on finishing writing this report, was ~500MiB on start of
writing this report), and is writing a significant amount of data to an HDD,
making the entire system slow. balooctl6 monitor simply prints ": Ok" forever.
STEPS TO REPRODUCE
Should note that I am not certain that these are the steps that cause this, but
I'd assume it is as this issue appeared shortly after doing these steps.
1. Copy the entire /home directory to a folder on a different drive.
2. Make the main partition on that drive mount as /home, moving some
directories around to make this feasible
3. Switch the distribution, overwriting everything in the system partition
4. Use the computer as normal. As time goes on, baloo_file_extractor will
progressively take more resources.
OBSERVED RESULT
baloo_file_extractor slowly takes more and more resources, and ": Ok" is the
only thing shown in the monitor.
EXPECTED RESULT
baloo_file_extractor would use roughly the same amount of resources as it
indexes
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
ADDITIONAL INFORMATION
Here is the output of balooctl6 status:
Baloo File Indexer is running
Indexer state: Indexing file content
Total files indexed: 5,551,335
Files waiting for content indexing: 1,568,892
Files failed to index: 0
Current size of index is 7.79 GiB
...and balooctl6 running for one minute
Press ctrl+c to stop monitoring
File indexer is running
Indexing file content
: Ok
- 358 repeating lines removed for brevity -
: Ok
^C
Notably, less lines are printed when making it output to a file instead of just
outputting to the console directly.
Bug 400704 seems related, but not the same, as that bug had high CPU usage as
well as high disk usage, while this has high RAM usage instead. Bug 354636 also
seems similar, however the trigger for that was instead updating to framework
version 5.80.0, while I have been using 6.10.0 for several days now with no
issues. The only change in baloo in 6.10.0 was removing an unused member, so I
doubt that update is causing it.
--
You are receiving this mail because:
You are watching all bug changes.
