https://bugs.kde.org/show_bug.cgi?id=444520
Bug ID: 444520
Summary: Baloo content indexing resurrects itself after being
killed *and* disabled
Product: systemsettings
Version: 5.23.2
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_baloo
Assignee: baloo-bugs-n...@kde.org
Reporter: adam.m.fontenot+...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
Just in time for Halloween, Baloo returns from the dead to haunt the living.
Suppose a user encounters one of the many common performance issues caused by
Baloo, like the one I describe here:
https://bugs.kde.org/show_bug.cgi?id=380456#c14
They are likely to try to pause Baloo using system settings, but this
(frequently? always?) doesn't work, as I describe in this bug:
https://bugs.kde.org/show_bug.cgi?id=443693
So they're likely to try disable indexing file content (while leaving "Enable
File Search" checked. They may even `kill -9 baloo_file_extractor` and reboot
just to be sure it's dead.
Sooner or later, whenever Baloo kicks back in, it may also restart indexing
file content, despite being disabled. On the computer this happened on, I
caught baloo_file_extractor hanging (again) with 100% CPU use and several GB of
memory eaten on one particular PDF file, the same issue that triggered my
comment here: https://bugs.kde.org/show_bug.cgi?id=380456#c14
To state the obvious, Baloo should *never* resurrect an already-killed file
extraction if "index file content" is disabled.
STEPS TO REPRODUCE
1. Enable File Search and content indexing in system settings.
2. Add a file to a directory indexed by Baloo which will cause
baloo_file_extractor to hang for a while and consume system resources. (There
are lots of examples of such files; because Baloo uses external libraries to
extract file contents, e.g. poppler, it's dependent on them to be well behaved
with the files they open.)
3. While baloo_file_extractor is trying to extract text from the file, kill it
manually and disable file content indexing in the settings.
4. Wait a while. (In my case, at least one reboot had gone by since disabling
content indexing.)
OBSERVED RESULT
Baloo appears to resume the partially completed indexing process that the user
previously killed, including indexing files - in particular the file or files
that were causing problems for the indexer.
EXPECTED RESULT
Baloo should respect the changed settings and not try to index the content of
any files.
SOFTWARE/OS VERSIONS
Linux: Arch Linux x86_64 (kernel 5.14.14)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
