Bug 377715 - Krunner consumes a lot of CPU since I start typing
Summary: Krunner consumes a lot of CPU since I start typing
Status: RESOLVED FIXED
Alias: None
Product: krunner
Classification: Plasma
Component: filesearch (other bugs)
Version First Reported In: 5.8.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-17 08:45 UTC by Karel Kozlík
Modified: 2018-10-31 18:00 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karel Kozlík 2017-03-17 08:45:49 UTC
Once I hit ALT+F2 and start typing into krunner the krunner CPU usage is increased to 80-90%. It does not go low until I kill krunner. This is reproducible always.

Once I have disabled all modules (in krunner settings) that search through files, emails and contacts the krunner start behaving normally.

Note: I have disabled baloo some time ago in system setting -> search -> file search

It seems the guy here experience the same issue: https://forum.kde.org/viewtopic.php?f=289&t=132775
Comment 1 Stefan Brüns 2018-10-31 18:00:30 UTC
File search is run out-of-process since https://phabricator.kde.org/D7404

If krunner is still consuming 100% CPU, this is no filesearch issue.

If the baloorunner helper is consuming 100% CPU, it is as filesearch/baloo issue. In this case, please reopen and move to component frameworks-baloo.