https://bugs.kde.org/show_bug.cgi?id=358956
Bug ID: 358956
Summary: Uses very much CPU while baloo_file_extractor forks
itself
Product: Baloo
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: m...@vhanda.in
Reporter: josephomor...@verizon.net
CC: pinak.ah...@gmail.com
Current versions:
kf5-baloo-libs-5.18.0-1.fc23.i686
kf5-baloo-5.18.0-1.fc23.i686
baloo-libs-4.14.3-5.fc23.i686
kf5-baloo-file-5.18.0-1.fc23.i686
baloo-widgets-15.12.1-1.fc23.i686
baloo-akonadi-4.14.3-5.fc23.i686
Process baloo_file runs baloo_file_extractor. Then baloo_file_extractor forks
itself. The new fork opens no files, but causes original baloo_file_extractor
to over-use CPU. Process baloo_file then runs a apparently-bogus fork of
itself.
Killing the forked baloo_file_extractor causes over-use of CPU to cease.
Killing the forked baloo_file process causes all baloo_file* to stop
altogether.
Reproducible: Always
Steps to Reproduce:
1. Log into Plasma 5
Actual Results:
baloo_file_extractor begins to hog CPU as described in "details" above.
Expected Results:
Nothing should be hogging CPU.
I have read about various "solutions", including blacklisting home folder, but
all seem to just be workarounds that merely kick the can further down the road.
--
You are receiving this mail because:
You are watching all bug changes.
