Bug 361696

Summary: baloo_file_extractor is at 100% CPU after login until killed
Product: [Frameworks and Libraries] frameworks-baloo Reporter: Najjar <abderrahman.najjar>
Component: Baloo File DaemonAssignee: Pinak Ahuja <pinak.ahuja>
Status: RESOLVED DUPLICATE    
Severity: crash CC: aspotashev, christoph, pinak.ahuja
Priority: NOR    
Version First Reported In: 5.20.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Najjar 2016-04-12 22:59:49 UTC 
"pacman -Qs baloo" returns baloo 5.20.0-1, baloo-widgets 15.12.3-1, milou 5.6.2-1

baloo_file_extractor occupies a core at 100%, and it's doing nothing. The page at https://community.kde.org/Baloo/Debugging doesn't wield results

"balooctl status" returns
Baloo File Indexer is running
Indexer state: Idle
Indexed 37504 / 37597 files
Current size of index is 219.25 MiB

And the number of files doesn't change

$ps aux | grep baloo_file
ion        968  0.2  2.0 5600856 125280 ?      SNl  22:11   0:06 /usr/bin/baloo_file
ion       1175 98.4  5.5 5921464 337004 ?      RNl  22:12  38:38 /usr/bin/baloo_file_extractor
ion       2431  0.0  0.0  10756  2256 pts/1    S+   22:51   0:00 grep baloo_file

htop shows baloo_file -> baloo_file_extractor -> 2 baloo_file_extractor

It only stops when baloo_file_extractor is killed, but the functions of baloo are limited after that

Reproducible: Always
Comment 1 Najjar 2016-04-12 23:01:16 UTC 
Bug 349096 said that's it's FIXED now. It might be a regression

I should also point out that memory consumption isn't high here, and it doesn't keep growing
Comment 2 Najjar 2016-09-04 15:43:23 UTC 
The issue is still in 5.25.0
Comment 3 Christoph Cullmann 2016-09-12 11:48:32 UTC 

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