How to diagnose high CPU use?

42 views
Skip to first unread message

Diggory

unread,
Feb 26, 2021, 8:26:34 AM2/26/21
to Quicksilver
Hello, I love QS and have used it for years. 

Recently I find that it's using way too much CPU, even when idle.  I'm loathe to wipe the prefs and "application support" folder as I fear it will lose all it's learned over the years.

Is there any way to diagnose what is causing the CPU use?  Perhaps it's one of the plugins.

Here's a sample.


Sample of Quicksilver.txt

Rob McBroom

unread,
Feb 26, 2021, 8:41:30 AM2/26/21
to Quicksilver
On 26 Feb 2021, at 7:03, Diggory wrote:

> Hello, I love QS and have used it for years.
>
> Recently I find that it's using way too much CPU, even when idle. I'm
> loathe to wipe the prefs and "application support" folder as I fear it
> will
> lose all it's learned over the years.

In general, when you’re not actively using it, Quicksilver seems to
spend most of its time scanning the list of running apps. That happens
whenever the active application changes. It does this mainly to figure
out the current scope so it can enable/disable the appropriate triggers.
Of course this happens frequently, but when I say “most of its
time”, we’re not talking about much CPU use really.

> Is there any way to diagnose what is causing the CPU use? Perhaps
> it's one
> of the plugins.

Taking a sample is a great start. 😀

In this case, it looks like it’s the Safari History catalog preset. I
disabled that a while ago and would recommend most people do the same. I
don’t remember if it was CPU use in my case, or just all the noise it
adds to the catalog interfering with day-to-day searches.

With that preset disabled, you can still access the history in QS by
selecting Safari, hitting → or /, selecting History, then hitting →
or / again. Just be prepared to wait for all that CPU work in real-time
when you do.

--
Rob McBroom

Diggory

unread,
Feb 26, 2021, 11:07:38 AM2/26/21
to Quicksilver
Thanks so much.  QS was regularly at the top of Activity Monitor when my machine was idle, it's now not even on the first page and is using a rational amount of CPU.

Have a good weekend and thanks for your ongoing work on QS.

Reply all
Reply to author
Forward
0 new messages