https://bugs.kde.org/show_bug.cgi?id=443547
Bug ID: 443547
Summary: Baloo_file_extractor uses all available memory and
never finishes running
Product: frameworks-baloo
Version: 5.86.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: vera...@protonmail.com
Target Milestone: ---
Created attachment 142299
--> https://bugs.kde.org/attachment.cgi?id=142299&action=edit
screenshot of system monitor showing high memory usage
SUMMARY
I recently downloaded a backup of my gmail account-- a large .mbox file of
around 2.8GB. After that time I noticed performance stuttering, intermittently
severe and causing the screen and cursor to lock up for a second or two at a
time, and high memory usage-- consuming all 8GB of my laptop's memory even with
no applications running.
System monitor suggests that Baloo_file_extractor is taking up all available
memory at any given time. CPU usage by baloo_file_extractor appears to range
typically between 4-12.5% (Intel i5-8250U (8) @ 3.400GHz) and memory usage
easily greater than 5GB depending on the number of other applications running.
running "balooctl status" gives the following output:
Baloo File Indexer is running
Indexer state: Indexing file content
Indexing: /home/.../All mail Including Spam and Trash-003.mbox
Total files indexed: 28,114
Files waiting for content indexing: 4
Files failed to index: 0
Current size of index is 526.02 MiB
Believing that the large file was taking a while to index and would eventually
finish on its own, I allowed it to run in the background, but after a day and a
half since I initially noticed the issue, it is still running and shows that it
is still stuck on this file. (I would attach it, but sharing a file with all of
my emails in it is a major concern). Restarting the PC appears to have no
effect.
STEPS TO REPRODUCE
1. Appears to start from the moment the OS loads
2. Possibly the result of a large .mbox file on my system
3. Suspending and disabling balooctl, then restarting the machine, caused
memory usage to return to normal
4. enabling balooctl again caused baloo_file_extractor to start and take up all
available memory
OBSERVED RESULT
High memory usage and noticeable OS performance issues. Indexer does not finish
after many hours of uptime.
EXPECTED RESULT
No OS stuttering while running in background.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.10.70-1-MANJARO (64-bit)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
