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 Jan 31, 2025 8:44 AM

Okay, I have a new hypothesis as to what's going on here with corespotlightd. This process is one of at least four that are responsible for macOS's Spotlight functionality. The three others are mds, mdworker, and md_stores. I cribbed the following descriptions of these three processes from the HowToGeek website:


The two processes [mds and mdworker] are part of Spotlight, the macOS search tool. The first, mds, stands for metadata server. This process manages the index used to give you quick search results. The second, mdworker, stands for metadata server worker. This does the hard work of actually indexing your files to make that quick searching possible.


And for md_stores, from the TechNewsToday site:


Mds_stores is the core indexing process of the macOS. On normal days, it usually takes up a noticeable [sic, probably should be un-noticeable] amount of CPU. However, when you reinstall your OS or add new files/directories, your system will automatically start to reindex these new databases, which sees the mds_stores CPU usage skyrocket.


The macOS Spotlight feature makes use of two processes for indexing the system database; mds and mds_stores. The mds (Metadata Server) process is responsible for tracking and recording files and folders in your operating system. md_stores then compiles and manages these mds metadata, which Spotlight later uses for searching certain documents within your OS.


So it may be that corespotlightd is in fact an unwitting victim of other processes' having gone awry. On my two Intel systems, by three months after installing macOS 15.0, metadata associated with Spotlight located at ~/library/metadata had reached half a terabyte on both systems. It sounds like this data was actually written out by either mdworker, mds_stores, or both. And then, corespotlightd has to wade through these gigabytes upon gigabytes of metadata to actually produce search results, and as that task gets harder and harder with more and more metadata being produced, eventually Spotlight search results (which includes search and smart folders through Mail) degrade to the point of uselessness.


While I haven't managed to halt the rapid growth of metadata on these two Intel systems (Apple Silicon Macs still have the issue but to a much milder degree), simply deleting the metadata out of the ~/library/metadata/Corespotlight and ~/library/metadata/SpotlightKnowledgeEvents (while leaving the folders themselves intact) resulted in a near-immediate improvement in three areas: greatly reduced use of storage space; vastly improved search results; and much lower processor utilization by corespotlightd.


As noted, this metadata still continues to pile up (especially if I have a large (>5 MB) Pages file open). But if I have to empty out these two folders once every few weeks until Apple resolves the issue, that's not the end of the world).


346 replies

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




Feb 4, 2025 2:56 AM in response to SBML

Hi, I am new Reading this post and writing. I started having these kind of problems a couple of months ago. My MacBook Pro is from June this year, so less than one year old.


I have checket and I also have a store.db file of 17,51 Gb and another one of 1,91 Gb.


What soul I do about it? Can I just delete them?


Thank you ver much!

Feb 6, 2025 2:39 PM in response to ericmurphysf

Currently trying this out to fix that bug myself, and I have absolutely no idea what I'm doing. So I just want to make extra sure I got what you're saying. Now when you said deleting the metadata out of Corespotlight and SpotlightKnowledgeEvents, can I just delete everything inside those folders? Not working with Terminal here. Or keep the folders inside intact and just delete the lists and whatever is in there? Thanks!

Feb 6, 2025 2:43 PM in response to fronesis47

fronesis47 wrote:

But before I do that, I just have to say that Apple's "sort by rank" default option is a nightmare: it just makes the thread seem like meaningless nonsense, even though so many here are trying hard to solve the problem together.

With respect to this comment: yes, the "sort by rank" sorting isn't just useless; it's actively detrimental to actually following any kind of conversation. And to make matters worse, it's the default.


You can, however, sort by more useful orders, such as oldest first, newest first, etc. But the only place you can do that is on the first page of the thread, where the option is placed inconspicuously below the OP. It took me years of using Apple's community fora to even find this option.

Feb 8, 2025 2:42 AM in response to AshkaTheMoltenFury

Thank you for this. I tried it and things were actually looking promising. After 25 minutes though I decided to make an edit on my 1.3MB Pages document just to see if it would continue behaving, and unfortunately it did not. After about a minute CPU usage spiked greatly and the disk began writing immense amounts again. When the document wasn't touched at all however after opening, the system behaved (like 99% so). Definitely the most effective thing listed so far but unfortunately it still goes downhill after the first edit.

Feb 8, 2025 1:18 PM in response to fronesis47

I agree with Mitch Stone: it would be good to know if other documents (such as Numbers files) cause the same problem, and to see what happens with a new user.

THANK YOU to sugarskyline for showing me how to change the default presentation of the message board.

During all my trials and tribulations with this issue I've had several Numbers files open on various computers (I almost never use Keynote). Most of the Numbers files are not very large (half a megabyte or so), but one is nearly a hundred megabytes. That's mostly embedded graphics though, and I'm not sure how much indexing gets done on graphics.


In any case, Numbers files do not appear to make either corespotlightd or Spotlight metadata spike. YMMV, naturally.

Feb 9, 2025 3:03 PM in response to ericmurphysf

ericmurphysf wrote:

I have another question: do people with Apple Silicon systems ever see the size of their Spotlight metadata folders decline? I've got two Intel systems and two AS systems, and while I never have seen these folders' sizes shrink (other than when I manually delete them) on Intel systems, I often see them get smaller on their own on AS systems, especially on my M2 Max MBP.


I can keep an eye out and report back! 🙂

Feb 9, 2025 3:41 PM in response to fronesis47

Thank you for this clear summary. I have developed this problem. I AM using large Pages files. The problem developed after one of the fairly recent system updates. I'm on an M2 Air 8 mb memory running 15.3. I am a heavy but ordinary user who is NOT comfortable deleting random files or using Terminal. Can you give us some simple instructions until APPLE fixes this problem. As the computer is quite Unusable at this point. It also has started crashing with the same error (can't recall - but something about devices not loading upon reboot).

Feb 9, 2025 4:12 PM in response to Bets

For those who can't find your Library file go to Finder, hold the option key while clicking GO - your Library folder will appear. Still concerned about just deleting the Corespotlightd file - but at least I've found it. Thanks for the discussion - I hope Apple does something about it. perhaps modify Pages somehow.

Feb 10, 2025 9:10 AM in response to Mitch Stone

Alongside the spotlight issues, has anyone else been having problems with Pages itself falling over?


I have a few quite complex documents and have been finding two things have increased in parallel: all the beachballs/spotlight issues AND Pages falling over and reporting to Apple.


From my perspective, Pages seems to fail when, after making an edit which might itself be trivial, I scroll. Pages disappears, then I get the windows asking if I want the report to go to Apple (and I always do allow that), and if I want to let Pages restart.


Time after time, Pages only loses the tiniest bit of editing. (Hats off to Apple on that score.) But it takes an annoying time to be able to get back to editing the document again.


I'm adding in to this thread because my perception is that both issues have worsened which makes me wonder if they are intertwined?


Given the vast number of automatic reports from me alone, I'd have hoped Apple would notice and fix the Pages issue. And, if it is related, maybe fix the spotlight issue by so doing. Or vice versa.


I also want to appreciate the efforts put in to get the spotlight issue resolved.

Feb 10, 2025 12:24 PM in response to ericmurphysf

That's what worries me about this problem. With the manifestation of it being so diverse and unpredictable despite the commonalities, it could make diagnosing and solving the issue much more complicated for Apple compared to standard bugs. Ironically, when Apple Support was asking me to provide a screenshot, that was the very first time since I bought this Mac that Pages behaved. I had to wait several minutes to get it to trigger again. Very bizarre.


Is it accurate to say though that everyone here was having a good time before Sequoia 15.2?

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.