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 Dec 31, 2024 11:01 PM

On my M4, tried

while true; do killall -9 corespotlightd 2>/dev/null && sleep 0.5; done &

this seemed to get rid of the process if run for a few seconds. But then opendirectoryd comes up and consistently uses about 20% of cpu.

305 replies

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.

Apr 28, 2025 10:22 AM in response to Mitch Stone

Mitch Stone wrote:

I will continue to recommend that we pay attention to real-world performance, rather than looking elsewhere for problems that may not actually be problems. The size of the metadata files may be related to the Spotlight bug in some way, but we don't have the technical information to know how


I agree with the basic sentiment here. The biggest issue is the slowdown caused by the corespotlight process running wild, not the size of the metadata folder. However,


  1. While it's not confirmation from Apple engineers, we have a large pile of anecdotal data concerning the link between the two. My system has never experienced slowdowns when the metadata folder was at a reasonable size. Whenever my Mac's performance has been degraded, my metadata folder was huge.
  2. At a certain point the size of the metadata folder itself becomes a "performance issue." For folks with a 256Gb SSD, it's not reasonable for MacOS to use up as much as half the drive (many people have reported that folder growing to over 100Gb) to store corespotlight metadata. This is a problem in itself.


I'm on a fast Mac (M4) and I use relatively small (less than 5Mb) Pages files, so it's rare that I have slowdowns. But that folder will sometimes reduce my available storage space from 240Gb down to as little as 50Gb. That's not right.



Jun 16, 2025 02:42 AM in response to Mitch Stone

Having had a period of relatively little impact, I've had terrible issues this morning. Using Numbers seems to be the biggest issue. A sheet of 448 kb and pretty simple except for being a pivot table.


M4 mini freezing repeatedly. And Spotlight folder bigger than ever.



I did have a Pages file opened - but even closing that - and idle Excel and Word instances - did not fix the issue. Only closing Numbers - and waiting - got me out of the mire.


This ridiculous size is making my drive look rather full.

Jan 7, 2025 09: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.

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.