And, generally-speaking, the “why?” behind the extra CPU usage is already known, too. I certainly don’t need extra CPU resources dedicated to telling me that something I’ve decided to run is using the CPU. I looked at the logfiles created by spindump/tailspind and they (basically) told me what I already knew: some process needed a significant amount of work done and my 6-year-old CPU took longer than some pre-set limit to do it. In the interim it would be tailspind and spindump consuming a majority of the CPU while the processes you actually want to run tried to squeak by. This would go on until finally everything had finished. The problem is that it would create a cascading scenario of constrained CPU resources where one app would run, then spindump/tailspind would run, consuming CPU of its own, causing other apps to run for too long, causing spindump/tailspind to fire up again … and so on and so forth. It’s this second case that kept happening to me, and possibly to you. Some application or process would consume maximum CPU for some period of time (30 seconds seems to be the general consensus), and then tailspind and spindump would fire up to take a snapshot of what was going on for future debugging purposes.

An application asks tailspind and spindump to take a snapshot of the state of that application and write it out to disk, or.

Mac os paste disabled