My OSX Finder eating all cpu in a busy loop, the situation is:
I connect to a samba in my home. I suspend without umount that samba.
I go to another place. I click the umount in Finder.
Then... oops, the fan spin up....
Finally, I use "top -o cpu" to find it's Finder that cause this trouble.
btw, why shouldn't "top -o cpu" be the default ?
Apple just work, if you work in the way they think. Of course, nothing can get rid of this, apple in no exception.
沒有留言:
張貼留言