baloo_file_extractor has recently started using a whole CPU thread on login. It just hangs there taking 25% of my CPU indefinitely (until I End Process). I have no clue what is causing it.
This sounds like a dupe of bug 370963. Either there's a file that it can't index, or it could be that you have a corrupted ~/.local/share/baloo/index file.
This bug report is too unspecific to take any action. In case the issue persists and you can provide more information, please reopen. Required information: - Are both baloo_file and baloo_file_extractor alive? - Whats the last file baloo_file_extractor was processing? - output of "balooctl monitor", output of "cat /proc/<extractor pid>/fd"
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!