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.

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 | # ]