https://bugs.kde.org/show_bug.cgi?id=488645
Bug ID: 488645
Summary: baloo_file_extractor high CPU usage, baloo stops
indexing
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.3.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: skierp...@gmail.com
Target Milestone: ---
SUMMARY
Baloo works OK for a few days then consumes a lot of CPU and stops indexing new
and changed files.
STEPS TO REPRODUCE
1. Wait for system fans to turn on.
2. Run top and ps, notice baloo_file_extr high CPU use
3. Look in journalctl
4. Run `balooctl6 monitor` in a terminal.
5. Create or modify a text file in an indexed location.
OBSERVED RESULT
baloo_file_extractor is consuming high CPU
[spage@fedlaptop]/tmp% ps alx -w -w | rg 'PID|baloo'
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME
COMMAND
0 1000 1831 1533 39 19 269117376 2660 futex_ SNsl ? 1:28
/usr/libexec/kf6/baloo_file
0 1000 266144 1831 39 - 269599760 70864 folio_ DNl ? 10:34
/usr/libexec/kf6/baloo_file_extractor
journalctl has no log output from baloo (I turned on kfilemetadata and baloo
logging in ~/.config/QtProject/qtlogging.ini). The last warnings are from
around the time the fans turned on:
...
Jun 17 15:49:10 fedlaptop baloo_file_extractor[266144]: kf.filemetadata:
Searching for external extractors:
"/usr//usr/libexec/kf6/kfilemetadata/externalextractors"
Jun 17 15:49:10 fedlaptop baloo_file_extractor[266144]: kf.idletime: Could not
find any system poller plugin
Jun 17 15:49:10 fedlaptop baloo_file_extractor[266144]:
qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime):
invalid nullptr parameter
Jun 17 15:49:10 fedlaptop baloo_file_extractor[266144]:
qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime):
invalid nullptr parameter
Eventually my fan shuts off and my system is responsive (baloo runs at low
priority), but baloo CPU usage remains 40-60% if I'm not active in other
programs.
balooctl6 monitor doesn't report indexing of new and modified files.
EXPECTED RESULT
CPU usage stays low.
baloo continues to index new and changed files.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1 (Wayland)
ADDITIONAL INFORMATION
The KDE warning in the journal could be irrelevant.
Unfortunately I can't tell what file baloo_file_extractor is indexing, if any.
It doesn't show up in `lsof -p <PID_OF_BALOO_FILE_EXTRACTOR>`, I think because
baloo_file and baloo_file_extractor communicate over a pipe. I'm not sure what
log output wil get baloo_file_extractor to report what it's doing. `strace`
outputs nothing for a while, then a lot of lseek/writev/write64 activity on fd
6, which is my ~/.local/share/baloo/index, a 5 GB file on a btrfs volume.
I don't know what else to do to debug this.
--
You are receiving this mail because:
You are watching all bug changes.
