Finder Issue - Scorching my CPU!

[MyLeftNut]

Hi all,

I am running a 17 PB Rev C with all the latest updates.

My problem is that Finder is hogging my CPU to such an extent the processor
overheats and the fan comes on very quickly.

I am running (llustrator/iMovie/QS/Suitcase) typically but not much else.
Looking at the Activity Monitor shows the CPU going beserk and the only way to stop it is to Force Quit. This doesnt seem to solve the issue. Is there a plist file or something I need to delete? Has anyone else experienced this?

 

[Daveway]

This occurs on my system from every now and then. What happens is that Finder locks up. If you relaunch Finder it will only lock up again. From experience a quick resetting of the PRAM solver the issue.


>>>restart>hold down command, option, p,r>wait for second chime.

 

[MyLeftNut]

Daveway,

Thanks mate, for the quick reply.

So hold down 4 keys (Command/Option/P & R)?
Do you know why it does this? If I can figure that out maybe I can avoid it.
Have you regularly had issues with this even after resetting PRAM?

Cheers

 

[MyLeftNut]

Arrrghh. Reset the PRAM as you suggested Daveway. No good. Finder is taking up 90% of the CPU cycles....anyone got another suggestion?
This is insane. I can think of any reason for this behaviour to happen from my machine....

 

[Daveway]

I asked the guy at an authorized reseller and he had no idea how to fix this problem. This seemed to work for me:

empty trash
repair permissions
reset PRAM & NVRAM

I think the problem is a corrupt file and it drives Finder crazy, I know I went through this for days!

 

[MyLeftNut]

Hey Dave,

Thanks for the reply. I have fixed it. After resetting the PRAM, repairing permissions, clearing trash and caches etc...still no luck. I have since deleted the finder preference file and this seems to have done the trick.

Not sure what the NVRAM is, wouldnt know how to reset it but at the moment the finder is working as it should, although I would like to know how it got corrupted in the first place. My suspicion is that there are font conflicts with suitcase getting in the way...bloody suitcase, it really should do a better job. I've had problems with it before...

Thanks for your help...