spotlightknowledged high resource usages lead to fast battery drain and overheating

I tried a few things:


  • Restarted my MacBook.
  • Removed the Macintosh HD from indexing and then re-added it for indexing.
  • Deleted the index completely and let indexing complete, which took only about 5 minutes.
  • For a temporary fix, I forcefully killed the process, but it respawned after a while when I used Spotlight again. So, I keep killing the process whenever it starts consuming too much resources.


A few things I’ve noticed about the problem:

  • The process doesn’t suddenly start consuming resources; it takes about a few minutes before the resource usage skyrockets.
  • Even if I let the process run for an hour, it still continues to consume resources.
  • Killing the process instantly respawns it, but the resource usage remains within the limit for a while.






[Edited by Moderator]

MacBook Air 13″, macOS 26.0

Posted on Oct 16, 2025 8:19 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 17, 2025 11:58 AM

Hey @Rohit_070_


I wanted to follow up with what worked for me in case it helps anyone else dealing with this issue.

I created a full Time Machine backup, then made a macOS Tahoe bootable USB using Apple’s guide Create a bootable installer for macOS - Apple Support (CA). I booted from the USB, wiped the SSD using Disk Utility, and restored from the Time Machine backup.


Since doing that, everything’s been running smoothly. I've been using the MacBook all day without any overheating or high resource usage, before the reset, spotlightknowledged was eating up 27GB of RAM and the machine was too hot to touch


Not sure if this is related, but I was on the macOS Public Beta over the summer. I switched to the Release Candidate, then eventually updated to the stable 26.0.1 build, maybe that transition caused something to break.

Hope this helps!


5 replies
Question marked as Top-ranking reply

Oct 17, 2025 11:58 AM in response to gratts03

Hey @Rohit_070_


I wanted to follow up with what worked for me in case it helps anyone else dealing with this issue.

I created a full Time Machine backup, then made a macOS Tahoe bootable USB using Apple’s guide Create a bootable installer for macOS - Apple Support (CA). I booted from the USB, wiped the SSD using Disk Utility, and restored from the Time Machine backup.


Since doing that, everything’s been running smoothly. I've been using the MacBook all day without any overheating or high resource usage, before the reset, spotlightknowledged was eating up 27GB of RAM and the machine was too hot to touch


Not sure if this is related, but I was on the macOS Public Beta over the summer. I switched to the Release Candidate, then eventually updated to the stable 26.0.1 build, maybe that transition caused something to break.

Hope this helps!


Oct 17, 2025 4:58 AM in response to Rohit_070_

Hey, I'm also facing this issue on my MacBook Air 13" M1 running macOS Tahoe.

I've tried force-killing the process too, but like you mentioned, it just respawns and eventually starts eating up a ton of memory, in my case, around 27 GB of RAM. I’ve also let it run uninterrupted to see if it finishes indexing, but no luck, it just keeps consuming resources indefinitely.

Super frustrating. Still looking for a proper fix.


[Edited by Moderator]


Oct 17, 2025 5:14 AM in response to Rohit_070_

1 - Search - Apple Community Re Docker application


2 - Size: 245.11 GB

Free: 68.81 GB

Available: 91.25 GB

From another contributor @etresoft regarding Free Space and Available Space 


Free vs available disk space huge differe… - Apple Community


Quote >>  “ The "available" storage is the amount of used storage that the operating system could automatically delete if it felt that it was really necessary. The "free" storage is the amount that you can actually use for something.


There are system processes that run in the background and automatically delete some of the "available" storage and convert it to "free". If you completely run out of storage, then those system processes will try a little harder. When you "delete" files you are just hinting to the operating system that you don't need those files anymore. The operating system will eventually remove them, but on its own schedule.


Certain tools will allow you to force the issue and manually clean up some of this storage and manually delete local snapshots. But that is only temporary. "  << End Quote 


3 - Google Chrome


Short and unpopular suggestion for some


 https://chromeisbad.com


May consider an alternative www.brrave.com which is essentially Google Chrome without the Google baggage 


Refer to the Posting by Respected Contributor @ John Galt 


Application memory error on my MacBook Pro - Apple Community


Refer to the Posting by Respected Contributor @ Kurt Lang


etrecheck... Mac running slow - Apple Community


spotlightknowledged high resource usages lead to fast battery drain and overheating

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