https://bugs.kde.org/show_bug.cgi?id=370963
Bug ID: 370963
Summary: baloo_file_extractor stalls searching while still
consuming 100% CPU
Product: frameworks-baloo
Version: 5.18.0
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: pinak.ah...@gmail.com
Reporter: stephan.herrm...@berlin.de
This may have started with the upgrade of Kubuntu to version 16.04 (16.04.1 to
be precise):
System is stressed by baloo_file_extractor.
I would actually like to give baloo a chance, so I looked a little deeper:
balooctl status shows a constant number of indexed files, here "Indexed 75139 /
201948 files".
The first number will never increase, although baloo_file_extractor shows in
top with high CPU consumption.
Next, I tried to figure out if it stops at a particular file, so I run
baloo_file_extractor through strace. Interestingly it never touches any files
in my home directory aside from some configuration files (and searching ~/bin
for some executables).
Here's the last interesting stuff before it goes into what looks like an
infinite loop:
stat64("/home/stephan/.local/share/baloo", {st_mode=S_IFDIR|0775, st_size=4096,
...}) = 0
stat64("/home/stephan/.local/share/baloo/index", {st_mode=S_IFREG|0664,
st_size=136454144, ...}) = 0
open("/home/stephan/.local/share/baloo/index-lock", O_RDWR|O_CREAT|O_CLOEXEC,
0664) = 15
open("/home/stephan/.local/share/baloo/index", O_RDWR|O_CREAT, 0664) = 16
open("/home/stephan/.local/share/baloo/index", O_RDWR|O_DSYNC) = 17
stat64("", 0xbfc509fc) = -1 ENOENT (No such file or directory)
stat64("", 0xbfc509fc) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/i386-linux-gnu/qt5/plugins/accessible/.", 0xbfc5066c) = -1
ENOENT (No such file or directory)
stat64("/usr/bin/accessible/.", 0xbfc5066c) = -1 ENOENT (No such file or
directory)
stat64("", 0xbfc509fc) = -1 ENOENT (No such file or directory)
stat64("", 0xbfc509fc) = -1 ENOENT (No such file or directory)
(quickly creating millions of entries of the last kind).
At one point lsof told me that baloo_file_extractor holds a handle to
.xsession-errors which was also growing very large, but I cannot prove that
this is due to baloo. Here's a typical entry in .xsession-errors (repeated no
end):
log_kioremote: RemoteDirNotify::FilesChanged
()
()
()
log_kioremote: RemoteDirNotify::FilesChanged
()
()
Reproducible: Always
Steps to Reproduce:
Running Kubuntu with no baloo-related configuration changes.
--
You are receiving this mail because:
You are watching all bug changes.
