Bug 358956 - Uses very much CPU while baloo_file_extractor forks itself
Summary: Uses very much CPU while baloo_file_extractor forks itself
Status: RESOLVED DUPLICATE of bug 358548
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (other bugs)
Version First Reported In: 5.18.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-03 15:34 UTC by Joseph O Morrow
Modified: 2016-09-12 11:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph O Morrow 2016-02-03 15:34:30 UTC 
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.
Comment 1 Joseph O Morrow 2016-02-03 15:39:30 UTC 
Used htop (tree mode) and ftop to monitor process behavior.

fedora 23

kernel: kernel-core-4.3.4-300.fc23.i686
Comment 2 Christoph Cullmann 2016-09-12 11:46:03 UTC 

*** This bug has been marked as a duplicate of bug 358548 ***