Continued corespotlightd process CPU overload issues

I am wondering if anyone has discovered any new ideas for stopping the corespotlightd process from hogging the CPU. According to Activity Monitor, the corespotlightd process often occupies more than 100% of the CPU load, sometimes spiking as high as 400% on my M2 Ultra Mac Studio. This problem has become so severe that it often pinwheels under normally non-intensive tasks. It can cause the video to flicker on my Studio Display. In one case it caused my Mac to kernel panic (crash).


I encountered this bug only after installing Sequoia 15.2, but having researched this issue extensively, I find that Mac users have identified it since at least macOS Ventura. So here are some solutions we don't need to hear again:


Reindexing Spotlight by adding and removing volumes in Spotlight Privacy. This provides relief only temporarily. Within hours the process is again grinding the Mac to a halt.


Killing the corespotlightd in Activity Monitor. Again, this is at best only a temporary solution as the process will reinstate itself.


A "clean" install of macOS. First of all, no such process really exists. The OS recovery process simply reinstalls a new copy of the System files. Nobody reports this as a fix. An internal drive wipe and reformat, and restore from Time Machine is also unlikely to help, as it simply returns your Mac to its previous state. If the corespotlightd problem results from a corrupted file, the problem will likely simply be recreated in your reinstall. "Nuke and pave" might solve the problem if it caused by a format or directory issue on your startup volume. This does not seem to be the case, but if anyone has permanently cured the problem by this method, please report it.


What we do need to hear is from anyone who has spent time with Apple Support on this issue and been provided with solutions that actually work, or has new ideas about what causes it. Feels like we're on our own here, since Apple seems to be stumped.



Posted on Dec 19, 2024 11:21 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 8, 2025 2:10 AM

Hi everyone. I also encountered this issue that corespotlightd was slugging down my M1 MBP 16GB (2021) so immensely that my system had a freeze for around 5-8 seconds every minute or so.


Reading that according to your findings it might be related to large Pages files it got my attention because I'm currently working on my Thesis and use Zotero with lots of indexing and caching. I assumed this might be the limit of this machine but that thought was strange because I worked on so much more taxing tasks and it just performed good enough that the operating system was still performant enough. My Thesis file currently only has half a MB (currently mainly text) so that can't be the issue I thought.


After working for days like this (it really gets frustrating) I decided to invest some time in troubleshooting again. Before that I tried to reindex Spotlight (through System Settings and Terminal) or cleared up some space but nothing did the trick. Also not even turning off Apple Intelligence which I thought could be the culprit made a difference. Until I stumbled upon some thread somewhere which just generally stated that deleting the Cache Folder in Library (Finder>Go>Go To Folder>~/Library/Caches) might help or not but it's generally not a bad idea to clean it out from time to time. Well I didn't do that for like 4 years! Which actually speaks for the rigidity of macOS.


I went to that folder and it had a size about 50GB and literally right after deleting it the freezes and the high CPU usage of corespotlightd went away. I now waited several hours to see if it was just something temporary but it seems like this was indeed the solution.


And I forgot to mention: I upgraded from 15.2 to 15.3 several days ago and it seems like something in the Cache became corrupted or faulty (be it system files or app files) and caused corespotlightd to go rampant.


So in short: give the cleanup of the ~/Library/Caches folder a try. It might help and solve this high CPU usage of corespotlightd. Hope this helps anyone.



179 replies
Sort By: 

Mar 6, 2025 12:38 PM in response to Mitch Stone

  • I keep activity monitor open and handy all the time. Glad I have two large screens.
  • Copying large page document to remove metadata has been helpful bandage, but no fix.
  • I have not noticed spikes in Word (because I don't use it much and was not paying attention to Word). My Metadata accelerated its increase one day, and that might have been related to opening Word document. Not sure. I'll watch.
  • I have noticed spikes, slow CPU when I make any changes in Apple Contacts, which is huge problem, because I use Apple Contacts often.
Reply

Jan 7, 2025 9:08 AM in response to Mitch Stone

I have 370Mbs down and 94Mbs up. Pretty sure it's not a network problem. Also, I was seeing virtually no network activity when the processes were 'stuck'. I'm now two days into updating to 15.2 (build 24C101) on my 64Gb M4 Pro Mini and the issue had not reoccurred once. FYI, I also have an 2017 Intel iMac running OS 13.7.1 on the same network and that has not had any problems with corespotlightd or processes getting stuck during this time. I'm going to attach a photo (screenshot obviously not an option at the time) of the two Terminal windows I had open to see what was going on. You can see 27 stuck processes, mostly PPID 1 so child processes of launchd which was also stuck. Here endeth my google-assisted technical expertise, I'm just adding it in case it helps someone figure out what's been going on.

Reply

Jan 18, 2025 1:31 PM in response to Mitch Stone

First - me too - started when I updated to Sequoia 15.2.


I'm on an M1 Mac mini. The problem started with pages - which I use extensively with very large docs. I have fiber internet, and consistently get 900+ kpbs up and down.


It began with lags on my mouse and keyboard - just in pages, and spread to all apple apps, and then all apps.


Force quitting corespotlightd and restart worked for a bit. Then it came back - quicker and quicker.


Tried deleting some, then all of the spotlight activities - which worked for a bit.

Additionally tried completely turning off Siri and Apple Intelligence.


It worked for about 30 minutes. And now it's back.


Has anyone found ANYTHING that actually works?


-- update - now this process has taken over the processing suck




Reply

Dec 29, 2024 12:33 PM in response to MgS_2012

I come from that far back as well!


The systems I worked on could originally be single or dual processor, later up to quad. And processor usage for a single process could almost reach 100%. With a maximum across all processes potentially approaching 400% on a quad. Which made sense.


But the precise meaning of 138% is far from obvious. Especially when we need to consider performance and efficiency cores. And how do GPU cores fit?

Reply

Jan 1, 2025 8:58 AM in response to Mitch Stone

I’m guessing that the backup and corespotlightd were competing for the same resources (disk) and that would contribute to a spike in both processes as each would demand access to the shared resource, and then the kernel has to mediate it so neither gets completely starved.

Reply

Jan 1, 2025 9:41 PM in response to briantf

I actually ran

nice -n20 bash -c 'while true; do killall -9 corespotlightd 2>/dev/null && sleep 2; done' &

this was actually running in the background consuming battery (at least less than corespotlightd would)

This horrid process not only is causing beachballing but is taking up ~60G in frivolous logs as well 🤬


b@Brians-MacBook-Pro-M4 CoreSpotlight % du -shc *


 28G	NSFileProtectionCompleteUntilFirstUserAuthentication
 
...

 27G	Priority


 56G	total
Reply

Jan 1, 2025 10:51 PM in response to Rollwagen

This was a no-go for me, I'm afraid. Several hours after turning off AI, I opened the triggering Pages document and within 15 minutes or so was right back in beachball city.

Rollwagen wrote:

I checked Activity Monitor on my M2 MBA 8 hours after turning off Apple Intelligence and the CPU usage for corespotlightd was 0.0% !


Reply

Jan 3, 2025 8:34 AM in response to MgS_2012

I can't add a great deal to what has been reported apart from that I do not have this issue on a Desktop running on an Intel processor, only on my MacBook Air with an M2 processor. One difference between the MacBook and the Desktop is that Apple intelligence software can't run on an Intel processor.


I did turn Apple intelligence off for an hour, restart it and after an hour the corespotlightd process has become dormant - maybe just a coincidence

Reply

Jan 3, 2025 9:31 AM in response to Rollwagen

I've found a couple of ways to reduce the process load, but it's always temporary. Deleting the plist as I first suggested does it for me, but perhaps because this plist is modified by the OS every night, the issue comes back the next day. Possibly any large processor demand is the trigger. For me, the process always falls back into a tolerable range 10-15 minutes after closing the triggering Pages document. Thanks for being our emissary to Apple Support. I know how time consuming this can be. Looking forward to your report!


Rollwagen wrote:

Turning off Apple Intelligence on my M2 MBA macOS 15.2 stopped corespotlightd from hogging the CPU, dropping the process from in excess of 250% of CPU to 0.0 % within 8 hours. However, when I went back into my Pages doc (currently 1.2 MB, stored on iCloud), I continued to experience the spinning rainbow wheel, although less frequently and for less time. I've also experienced hesitation in my other apps (including while typing this post!), but no spinning wheel. I've talked with a member of the Senior Support Team at Apple and have arranged for them to collect data for Engineering to evaluate. That happens this coming Tuesday (my schedule doesn't fit with theirs until then). As much as we all don't like it, it appears it's a problem we'll have to live with for a bit until Engineering can figure out what's happening


Reply

Jan 6, 2025 8:57 AM in response to Mitch Stone

After installing macOS 15.2 earlier today, I cannot reproduce the issue. Apart from a single Google Chrome Helper (Renderer) process massively hogging the CPU (which did not return after a force-quit), I've gone from having 27 stuck processes with corespotlightd hogging the CPU to zero stuck processes and corespotlightd very occasionally flashing up in the top-5 of the usage list then vanishing again. No more spinning beachballs. No data entry issues. Time Machine drive reconnected and working. Fingers crossed this has fixed the issue.

Reply

Jan 6, 2025 11:19 PM in response to SBML

Good to hear this update helped you, but I am running 15.2 on all of my Macs (3) and still have the issue on one of them.


SBML wrote:

After installing macOS 15.2 earlier today, I cannot reproduce the issue. Apart from a single Google Chrome Helper (Renderer) process massively hogging the CPU (which did not return after a force-quit), I've gone from having 27 stuck processes with corespotlightd hogging the CPU to zero stuck processes and corespotlightd very occasionally flashing up in the top-5 of the usage list then vanishing again. No more spinning beachballs. No data entry issues. Time Machine drive reconnected and working. Fingers crossed this has fixed the issue.


Reply

Continued corespotlightd process CPU overload issues

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.