Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

How to fix a high CPU usage issue with Quicksilver Apps
There's one application I particularly love on my Mac: it's Quicksilver. This week, for the first time ever, it started behaving oddly -- my PowerBook was getting hot very quickly, and a check on Activity Monitor showed me that CPU utilization was at 100%, with Quicksilver using a varying amount from 20% to 90%.

I tried quitting and reopening the application, deleting its preferences file, and manually rescanning my catalog: nothing seemed to work. However, while digging around on my machine, a quick search in the Library led me to the folder containing the indexes used by Quicksilver: /Library » Caches » Quicksilver » Indexes. I quit Quicksilver, moved the Indexes folder to the trash, and reopened Quicksilver ... and it worked! Everything came back to normal (and I could then empty the trash, as the old files weren't needed). You can read a bit more detail about the process in this blog entry. Hope this helps someone out there.
    •    
  • Currently 3.17 / 5
  You rated: 1 / 5 (6 votes cast)
 
[14,283 views]  

How to fix a high CPU usage issue with Quicksilver | 4 comments | Create New Account
Click here to return to the 'How to fix a high CPU usage issue with Quicksilver' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
How to fix a high CPU usage issue with Quicksilver
Authored by: operator207 on May 28, '08 02:33:46PM

I have had the same problem, but it was not due to caches needing to be dumped. It was due to the shelf and clipboard history. I had set it to remember 250 items. It worked great for awhile, but I believe once it got to 250, and attempted to dump, it would not. I moved it to 25 items, and restarted it. It calmed down, and has been running quite nice for the last month.





[ Reply to This | # ]
How to fix a high CPU usage issue with Quicksilver
Authored by: lucite on May 30, '08 01:38:59AM

I'm on Leopard with QS Beta 54 (3815) and it crashes on me regularly.

So I welcomed your hint. But I have no /Library/Caches/Quicksilver!!



[ Reply to This | # ]
How to fix a high CPU usage issue with Quicksilver
Authored by: miked378 on May 30, '08 01:43:11PM

I tried this, and it seems to have worked -- Quicksilver is now running at 0.6% or less of my Powerbook G4/1.67's CPU, which is the lowest it's run in ages. Thanks!

One quick thing -- at least on my machine (under 10.4.11), my Caches directory was in ~/Library/Caches/Quicksilver (i.e., in my User directory's Library directory, not in the root Library directory). Maybe that will help the previous poster, too.

Thanks!



[ Reply to This | # ]
How to fix a high CPU usage issue with Quicksilver
Authored by: srhenderson on Mar 20, '09 06:07:52AM
GAH!

Just as I was following this tip's suggested fix, I remembered that I had added a large external HD's root to Quicksilver's catalog.

When I added the external HD's root to Quicksilver, I also set it to catalog an infinite depth of folders. That catalog entry was responsible for over 375,000 items. DOH!

Before I corrected this, I double-checked that my problem was the indexing operation that was spiking Quicksilver's CPU usage.

To do that, I:

  1. I started Activity Monitor. This allowed me to watch Quicksilver's CPU usage.
  2. Called-up Quicksilver bezel UI, via the shortcut key
  3. While it was waiting for me to start typing, I pressed Command-R. At that moment, the UI began showing me a spinning in-progress indicator in the lower right-hand corner, and a CPU spiiked to 100%.
  4. I then pressed Command-Comma, to bring up QS' preferences, and then I removed the Custom Catalog entry.
  5. I then closed the preferences, and tried the above steps again to validate that things were better.
My issues was probably different that the one that other posters had (everything was working perfectly, except for the user).

But still, you may want to double check that you haven't added too much to Quicksilver's indexing burden. For example, the Developer Add-In might be causing Quicksilver to index a great number of source code files that you may not want Quicksilver to help you find.

[ Reply to This | # ]