Why is Spotlight using 98% of my MacBook Air CPU?
UPDATED: August 19, 2008 7:42pm
Problem solved. It was a hanging process that got triggered when I installed a new VPN client. The weird thing was it could only be killed via the command line and didn't show up in the Activity Monitor
This MacBook Air goes from decent, to bad, to terrible, back to decent and now into the ridiculous.Even when running zero applications there are pieces of Apple software that are doing very strange things. The latest issue is that Spotlight is somehow using 98% of my CPU horsepower and the total percentage used is 114.4% which really shouldn't be possible.
Any of you Mac guys out there have any ideas? I killed my replacement Thinkpad battery by accident when I didn't put it into suspend or hibernate.
Dave Rosenberg dishes up "Software, Interrupted" with nearly 15 years of technology and marketing experience that spans from Bell Labs to multiple start-up IPOs to open-source enterprise software companies. He is co-founder of MuleSource and currently serves as the general manager of Hardy Way. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can contact Dave via e-mail at softwareinterrupted@gmail.com or follow him on Twitter @daveofdoom. 




Pretty much that 98% that you notice on Spotlight, it can be also the status of the application, meaning that is close to finish indexing, or also saving. I think if you wait some time the process will finish and also your cpu resources wil go down to 10% or minimal expression.
- by kelmon August 21, 2008 6:15 AM PDT
- Spotlight will be quite intensive when it is indexing a drive for the first time or your Spotlight index has been reset so that it's doing it again. However, during normal use Spotlight should consume no processor time except when you are actively using it or a file has been created/updated (mine currently shows CPU usage of 0.0%). All I can think of is that Spotlight has a corrupted index or some such problem, so reseting the Spotlight index may sort the problem out. Try the following command at the Terminal:
- Reply to this comment
-
(6 Comments)sudo mdutil -E /
That will cause Spotlight to delete its existing index for your startup disk and start again. It will take a while for the index to be created but after that the Spotlight process should not consume any CPU resources.