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 9, 2025 10:26 AM

After the better part of another day thinking about and troubleshooting this issue, I am convinced that Eric Murphy's earlier hypothesis is correct. There's a bug in Sequoia, which anyone can replicate by following these 2 steps:

  1. Open a Pages file (and keep it open).
  2. Watch the size of this folder balloon: ~/Library/Metadata/Corespotlight


The larger that folder gets, the more likely it is that the corespotlightd process will start taking over the CPU and causing slowdowns for the Mac user. The corespotlightd process is what gets most people's attention, but it's only a symptom of the underlying problem whereby the spotlight processes (mdworker, etc.) write enormous amounts of data into the corespotlight subfolders.


The bigger the Pages file the quicker the folder grows in size; the more frequently one uses Pages, or leaves Pages files open, the worse the problem.


There is no fix until apple implements one, and the only viable workaround is to monitor the size of that folder and occasionally delete it.


One silver lining: it's not clear to me that there is any need to delete your spotlight index, to turn indexing off and on, etc. The problem stems from the size of that metadata folder, and you can alleviate the problem by deleting the folder. In my experience (having deleted the folder many dozen times), spotlight works just fine without rebooting, reindexing, or anything else.


I came up with my own way of dealing with this issue: I wrote a simple shell script that trashes the corespotlightfolder; then I added that as a service in launchd so that it can run regularly (maybe every 2 days).

190 replies
Sort By: 

Feb 28, 2025 11:06 AM in response to ericmurphysf

An update on my status. Similar problems to everyone else. I too have large pages files, several machines, and iCloud file storage and sync. Deleted spotlight metadata a few times. Helped for a while, then the problems returned -- large metadata folders, high CPU load, and that weird rhythmic spiking of the CPU usage.


This week, the mouse (old Logitech with usb dongle for bluetooth) lag was significant across several apps, beginning with pages. Thought my mouse batteries were the problem. Changed batteries. Didn't work. Changed mice - went through all 3 of my usb dongle-bluetooth Logitech mice, and then switched to my bluetooth only laptop mouse. The problems went away.


Got new bluetooth only mice, and also dumped the metadata again. CPU load has been low and steady, Corespotlight metadata folders have stayed under 10 GB for a week!


Yet another weird data point.

Reply

Feb 28, 2025 4:45 PM in response to drjz

I believe most of us are seeing this in Pages files larger than 10MB. But I from what we are hearing it seems that the size of the file (which can depend heavily on whether it includes graphics) is less the trigger than on how much it has been edited, as Pages attempts to keep track of every version. This is probably why the metadata files grow so large.


So, what I last suggested is Finder duplicating a Pages file that seems to trigger this issue. The duplicated file should not have the versioning legacy of the original. Since I started working with a copy of large (20MB+, 80k words) Pages file that caused me much grief, the problem has ceased. So now we'll see if anyone pays attention to this suggestion and tells us whether it does or doesn't work for them, too.



drjz wrote:

Could you please define large in "large Pages document"?

I had trouble with Pages files 3-6 MB. Since then, I deleted the metadata several time, narrowed Spotlight's scope, eventually to zero, turned off AI, and even switched to Word for a while. Obviously rebooted. Finally the CPU settled down. Now, I have turned Spotlight back on, turned on AI, and gone back to using Pages with the same 3+ MB files, so far no CPU problems. Magic!? (The System data is ridiculously large at 100 GB, but that is not a problem compared with the lag from an over-busy CPU.)


Reply

Mar 6, 2025 1:06 AM in response to Mitch Stone

Tried playing around with a Microsoft Word file that was an exported Pages doc and even though the system is seemingly calm at rest, if I was to make the smallest edit possible (literally just pressing space bar) the response is actually somehow much worse than if it were just a normal Pages file. There is also a new issue of the read amount being absurdly high alongside the high write speed (when editing a Word doc). The response I get from a Pages file is more gradual and irrespective of what I do, the response I get from the Word doc is 100% reactive. Each and every edit no matter how small or simple will trigger a massive CPU and disk spike. If I do nothing it goes back to normal, however the disk read will continue to be elevated for around 8-10 seconds. This is a file that isn't even in the iCloud Pages folder, it's completely offline.


Additionally, losing hope at this point that this whole issue will be fixed in the next update but of course I don't know for sure. This app was an amazing switch and I did get several months of use out of it before this issue arose but I still wish I was able to go through all the phases of my project before this happened. I was willing to eat the disk write damage to the SSD cause at least I could pretend like it's not happening but the CPU spikes so high that it makes the fans kick and it's legitimately not something I can work around.


If for whatever reason you simply need to be able to read/present your document with all comments and chapters intact, export to Word. PDF allows comments but not as intuitively. I'm actually shocked how much information is perfectly retained in the Word doc.

Reply

Mar 6, 2025 1:57 PM in response to Mitch Stone

Absolutely happening to me-- corespotlightd spilking CPU and system glitching

on brand-new MacBook Pro Apple M4 Pro running 15.3.1

started about 4 weeks after I migrated over. all problem solving failed. reset to factory settings- and no migration. same issue presented. brought back to apple- they did firmware reinstall and set back to factory settings. can now confirm this continues to happen when and only when I am running pages- generally my pages docs are re-edit of forms with numerous past editions. I quit pages and glitching and CPU spikes go away

Reply

Mar 6, 2025 2:02 PM in response to Mitch Stone

I already tried all the listed suggestions. And the issue seemingly does not manifest consistently for everyone. I know there's been a primary focus on system folders but that was always the lesser of my problems. The spikes I see aren't ignorable, they bump CPU usage up to a consistent 40%+ on an M4 Pro MacBook Pro unless I close the app. There is no way the app can be seen as usable when it's single handedly taking up nearly half the CPU power. Battery drainage is also significant as within minutes it's as high as if I was using video editing software. I would've ignored everything else if it meant I could get back to using this app cause I have things that need to get done at the end of the day and I'd much prefer to use this app as the primary choice but the impact on my machine beyond the SSD writes and deletable folders is way too much. Activity Monitor isn't why I can't ignore it, it's how I get met with immutable fan noise and system slowdown. These are also issues I have always had bundled together rather than it being something that appeared later after the system folder issues.


Also, in response to LAWM0N, I was using a Word doc in the Pages app, rather than using the Word app (I don't own it).

Reply

Mar 7, 2025 1:36 AM in response to fronesis47

How do you delete meta data folders? I'm really not tech savy, but I'm experiencing the same issues as other are talking about. I'm writing a thesis and when I open the pages document, which is very large, my computer starts to have intermittent lags and cursor freezes.


I would like to use a work around for now, until apple figures out a solution.



Reply

Mar 9, 2025 9:48 PM in response to ScottRichardson

ScottRichardson wrote:

I just experienced this issue and my ~/Library/Metadata/Corespotlight was 50GB when I first looked, and within an hour it was 60GB in size! I just deleted that, and my caches folder and it appears to have fixed the issue. Thanks for the wonderful folk in here who identified a way to fix it for now.

One thing I've noticed (and the actual figure may differ depending on your system architecture, memory, storage space, etc.) is that once Spotlight metadata gets to a certain size, its growth begins to snowball. On my system, and seemingly on yours, that size is ~50 GB. It might take one of my Intel systems eight or nine days from when I delete all the metadata until it gets to 50 GB, but from there it's rarely more than a few hours before it gets to 60.

Reply

Mar 9, 2025 10:50 PM in response to ericmurphysf

Out of curiosity, I performed another Get Info on my Corespotlight folder. It is now 12.2 GB. Looking back a couple of months into this discussion, I found I'd reported it back then at 37 GB. I have never trashed this folder. So it seems it can actually get smaller without user intervention.

Reply

Mar 9, 2025 10:55 PM in response to Mitch Stone

Mitch Stone wrote:

Out of curiosity, I performed another Get Info on my Corespotlight folder. It is now 12.2 GB. Looking back a couple of months into this discussion, I found I'd reported it back then at 37 GB. I have never trashed this folder. So it seems it can actually get smaller without user intervention.

This is definitely true on Apple Silicon systems. I've never seen it happen on either of my Intel systems.

Reply

Mar 16, 2025 4:05 AM in response to Mitch Stone

Hi! And here I was wondering why my two M2 Macbooks (one from 2023, other from 2025) and a brand new iPhone 16E all connected through a Cloud sharing one simple small 7-8 pages long Pages document which is almost always open on some of the device... keep bumping up CPU to 100-300% in Activity Monitor, having caused one of the computers to completely freeze and crash two times already and constantly heating up the other.


The Library/Metadata/CoreSpotlight folder is 50GB, the store.db files alone takes up like 8GB each. If I close Pages and just keep TextEdit open with an iCloud-shared file, the spotlightd process does sometimes come up and spike up to a 100 percent but at least the computer isn't hot to physically touch anymore.


What would you recommend, please? Reboots don't help, killing the spotlightd process in Activity Monitor helps only for a few minutes. Closing the Pages app helps but unfortunately I really need the document, it's the only reason why I didn't buy a pen and paper instead.


I'm a bit puzzled – these three Apple devices together in 2025 cost about as much as a new car but they're incapable of handling basic text editing computers in 1991 managed well? I'm really not used to a brand new Mac with nothing but 1 file in a text editor open running a spinning rainbow wheel while I try to write simple letters. Please help. Thank you so much!

Reply

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.

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.