Bug 194543 - krunner consumes too much CPU and memory
Summary: krunner consumes too much CPU and memory
Status: RESOLVED WORKSFORME
Alias: None
Product: krunner
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-05-29 14:49 UTC by Jon Nelson
Modified: 2018-10-21 05:08 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 Jon Nelson 2009-05-29 14:49:45 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    SuSE RPMs

watching the top CPU and memory consumers in top (or ksysguard or whatever), I see that krunner consumes a fair bit of memory (14MB), might be leaking memory, and periodically consumes 5-8% CPU. 

In top, krunner sits there with 540MB of VIRT and growing. 

KDE 4.2.3 on openSUSE.

kwin, plasma, and kopete are also thirsty but what is krunner *doing* all the time?
Comment 1 Dario Andres 2009-05-29 15:50:25 UTC
All the time? Even when you are not using it?
Have you tried to disable some of its plugins? (maybe some of them are faulty of this)
You can also try to restart it (run "kquitapp krunner" and then "krunner")
Thanks
Comment 2 Dario Andres 2009-07-07 20:21:00 UTC
Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-19 04:39:13 UTC
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!
Comment 4 Andrew Crouthamel 2018-10-21 05:08:12 UTC
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!