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

Feb 10, 2025 11:43 AM in response to Mitch Stone

Has anyone else noticed that upon restarting the Mac, without ever opening Pages, the disk reads and writes are barely anything at all, but after opening and closing Pages, it will continue to read and write varying low amounts of data at very random and frequent intervals? And seemingly in a very unpredictable fashion compared to if Pages was open? My Mac has been restarted for hours and the disk had so little activity going on. The graph was quite flat. Now after opening Pages and closing it entirely after just a couple of seconds, it won't stop writing very low amounts and reading random amounts of data. I've noticed this for days but today really seals it for me that I'm not imagining it. Once the bug is triggered it cannot truly be eliminated unless you restart.

Feb 10, 2025 12:44 PM in response to sugarskyline

I had been having problems before my upgrade to Sequoia. I am a heavy pages user with large docs. I began experiencing lag about a year before upgrading. As noted by another poster, the lag and freeze was most noticeable if I had made many edits, and was scrolling through the doc *without* hitting save. I was able to reduce the problems if I saved every minute or so while working.


Once I upgraded, the problems increased to pretty much any time I have a pages doc open - whether I've edited it recently or not, and no matter how little or big the file is. I've tried every solution listed here - most multiple times - they all work for a bit - sometimes for a longer, sometimes for shorter time period.


REALLY hoping they get this fixed soon - I use pages all the time, both while working with clients and as I'm preparing a manual for publication.

Feb 14, 2025 3:45 PM in response to Bets

I'm hoping to talk to yet another Apple senior advisor tomorrow (Saturday Feb. 15), not so much seeking a resolution for this issue as to provide Apple's engineers with as much detail about this issue as I can gather.


In pursuit of that goal, I have a question: is anyone seeing these large accumulations of metadata in the ~/library/metadata/CoreSpotlight/ and ~/library/metadata/SpotlightKnowledgeEvents/ folders (the latter is a separate folder on Intel systems) without using Pages?


In my experience, if I don't have a Pages document open, Spotlight metadata generally does not grow by more than a few hundred megabytes a day (which ain't nothing, but it's a lot less than the 10 GB/day or so I see if Pages is open). I'm curious if anyone has seen large increases in metadata despite not having Pages in use.

Feb 17, 2025 4:03 PM in response to fcoteb

A couple of other observations that are specifically about Spotlight's effects on storage space and battery life on M-series Apple laptops:


First: it seems that while Spotlight processes definitely pile up quite a bit of metadata on M-series Macs, including laptops, it's not as severe as on Intel Macs. One of the reasons it seems to be less severe is that while on Intel Macs I have never seen the CoreSpotlight folders referenced on this thread ever decline in size unless I manually remove data, I'd say that I see day-to-day declines on M-series Macs about 40% of the time. Sometimes the declines are as much as 50% from the previous day.


Second: even though Spotlight metadata does not accumulate on Apple Silicon Macs the way it does on Intel Macs, Spotlight in combination with Pages seems to have a dramatic effect on battery life while the system is ostensibly "sleeping."


If I have a Pages document open on my M2 Max MBP overnight, that will drain the battery by between thirty and forty percent. If I quit Pages, I won't typically see any drain overnight, i.e., the battery will still be at 100% if I charge it after my last use of the day. There doesn't seem to be a way to prevent M-series Macs from doing all kinds of stuff while they're ostensibly asleep with the lid closed ("Power Nap" doesn't seem to be a function you can disable), but in any case Spotlight appears to continue to index the filesystem even while the laptop is asleep if a Pages document is open on it.

Mar 6, 2025 11:20 AM in response to sugarskyline

Did you try my suggestion? For me, it actually did help a lot. I'm not sure I understand the resistance to it, given the simplicity and apparent effectiveness. I'd really like to know if it works as well for others as it did for me.


Also, I realize it's easy to obsess over the Activity Monitor once you are aware of the issue. I sure did. But I would remind everyone that seeing the process spike occasionally in AM is not the issue that drove us to this discussion; it was a noticeable hit to system performance and occasionally even kernel panics. If you are not experiencing either of these issues, then this problem has at least become manageable until Apple figures out a fix.


So (again) my workaround suggestion is: Finder copy the Pages file that produces the issue for you and work with the copy. Give it a try. What's the worst that can happen?

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.

Mar 16, 2025 8:58 AM in response to ericmurphysf

Thanks Erik. Unfortunately before I had a chance to read that I used a suggestion from an Apple Developers Forum where there's a thread on the subject with a seemingly legit solution. A user pasted a set of commands to run for Terminal which I ran and that included sudo rm -rf... which, possibly because they contain a typo I hastily overlooked, successfully wiped out not only the entire Metadata folder but my entire computer - all my files left unbacked up at that point as I was trying to move things around for the Cloud when this Spotlight bug kicked in and made the computer hardly responsive. Oh well.


The lesson here - anyone looking for suggestions to fix this, please be very careful what you try. People are capable of giving you absolutely destructive instructions even on the developers forum. Please double-check anything before you run anything.

Mar 31, 2025 12:05 AM in response to fronesis47

I bought a new M4 MacBook Air [10c/24GB/1TB] Running MacOS 15.3.2] and did not use Migration Assistant. I did turn iCloud Drive on, but I did NOT turn on Desktop and Documents Folders. So I have no data on my SSD, just the OS. I opened large Pages (475 kB) and Numbers (35MB) files from my iCloud Drive that I update through the day and so they are open most of the time. In activity monitor, I noticed that Pages was spiking up to 50 to 70 % when running in the background (whereas the large Numbers file was at 0.4%). Next, I noticed the OS was laggy when command tabbing between apps and saw that corespotlightd and/or kernal_task were sitting at > 200%! (As I type this, corespotlightd is at 126.7%). I reported all issues via Apple's Feedback page. I have also had Numbers doing SBBoD and/or crashing and Apple News has crashed several times too. This behaviour is persistent since I set the Mac up on March 13th 2025.



Apr 1, 2025 6:43 PM in response to Mitch Stone

I have experienced CPU Overload since year end. Grateful for this support thread. I have to move 20-25 GB to Trash from two Metadata folders EVERY DAY! Otherwise overload issues slow computer immensely and geometrically.


While I remain grateful for this bandage method, I want permanent fix. Apple Support had me delete hard drive at year-end, because they could not figure out problem (they should have seen this thread!). I'm still suffering from that unnecessary action.


We've had one Sequoia update since then, but NO improvement to CPU Overload issue. I want to hear status report FROM APPLE! This seems clearly to be software error and will need software fix. The seasons are passing. Time's up! Apple needs to fix this or upgrade my CPU to Apple Silicon, which seems immune to this problem


iMac > 3.8 GHz 8-Core Intel i7 > Sequoia 15.3.2 (24D81)

Apr 3, 2025 6:29 AM in response to KWiPod

My M4 mini has been behaving perfectly since Sequoia 15.4. When I first got it, it was extremely fast for my purposes (mostly Pages and web) - and it got slower and slower. I am very pleased it is back to how it should have been all the way through.


My M1 MBP had never been as bad - and it too seems to be altogether somewhat faster.


Hoping this continues to be the case - and it fixes the issues for everyone else.

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.



May 22, 2025 10:59 AM in response to Bets

Update May 22: Still running 15.4.1. Delayed updating to 15.5.

I've cut back my Pages use considerably, using other options. Editing PDFs, Using Notes or e-mail.

I AM still using Pages, but am mostly limiting use to documents created this Spring.

I've continue to use the above 2 step method. Although I have FORGOTTEN to close Pages recently and come back to find NO increase in Corespotlight folder size overnight. So that's great!

Also, why I am concerned about updating to 15.5 as I've seen others with problems.

Of course, security updates may be MORE important.

APPLE - any responses yet?

Jun 3, 2025 12:15 PM in response to PolyRod

The wide variation of experience with this bug is vexing. In my case I was easily able to verify that iCloud was definitely not a factor. Others find evidence that it is, for them. This brings me back to my theory that it is document-specific and that moving or duplicating the document can mitigate it, at least in some cases.


Maybe the forthcoming macOS update (which we are hearing will be called Tahoe) will finally fix it for everyone. We can hope, at least.

Jul 21, 2025 4:39 PM in response to Privacy86

Hmm. In theory (at least), a complete restore from Time Machine should not help, as it restores the Mac back to its prior state -- problems included. Your experience of restoring back a few days seemingly providing relief, even temporarily, is interesting. My original theory about this issue involved a bad preference file, and I found that deleting the one for Spotlight helped my situation temporarily. The issue always returned by the following day. The OS writes to this file overnight apparently for automatic routine system maintenance. Nobody else seemed to have any success with this temporary solution, but I am wondering now if it doesn't have some merit after all.

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.