Safe to kill spindump? (Older/slower machines) I have an old Mac, where if an App take some time to load (slow HD), the spindump kicks in, completely disabling the machine for close to 10 minutes.

There is one post on the web warning that killing spindump can cause some corruption, so, better safe then sorry.

Would be great if there was a way to not run spindump on specific Apps, or give them more time before declaring them as 'unresponsive', but I doubt there is.

Is it safe to just kill the process? Is there a safer way (like asking its parent to to so)?  



Minor update:
Seems that the same App that triggered the spindump, no longer does so. It still takes the same time to load, but that no longer triggers spindump.
If you're in a similar situation, it does quiet down eventually (as apposed to launch on every stall). It has happened about 3-4 times (one for each spinning ball), each time it took around 3-8 minutes to calm down and release the RAM.
It's probably safe to even disable them if you are not interested in the generated system analytics. Full procedure to do so is documented on Disable tailspind and spindump to Speed Up your Mac. In a nutshell:


Disable SIP
Unload/rename LaunchDaemon for spindump

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.spindump.plist
sudo mv /System/Library/LaunchDaemons/com.apple.spindump.plist{,.bak} 

Do the same for com.apple.tailspind.plist
Enable SIP


You probably need to redo this with each macOS update.