A few times a week, the Finder on my Macbook shoots up to around 100% CPU use, and the fans start blasting.
I've done everything I can think of - repaired permissions, rebooted, trashed preferences, turned off "show preview" in view options, audited the Activity Monitor for unnecessary processes, scoured the Console for errors, restarted the Finder, and a lot more. Eventually it subsides, and I assume that the source of the error was the last thing I changed.
But it's doing it again now, and I am at a loss. I wish there was a way to "get inside the Finder's head" and see what it's doing. I've tried running a sample of the Finder process in Activity Monitor, but honestly I don't know what it's doing, much less how to interpret the output.
That's really my hope: that someone can explain a better way to investigate CPU spikes like this, not just in the Finder, but any runaway process. There are certainly plenty of details that might help you all diagnose this specific case, but before I spew out even more probably-irrelevant information, I thought I'd see if anyone has general tips for diagnosing this sort of thing.
This is my first Stack-anything post btw, so please be gentle. Thanks in advance!