Just lately it seems that whenever I do anything with large files (such as opening a picture from my digital camera in Preview) the Finder starts hogging the CPU and won't stop until I relaunch it (this is even after the file in question has been closed). I tried running fs_usage in the terminal and got the following output:
Code:
16:56:06 read 0.000048 Finder
16:56:06 read 0.000004 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000008 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
16:56:06 read 0.000003 Finder
which seems to show that it's accessing
something but doesn't tell me what it is. Even deleting the file I just opened and closed doesn't seem to stop it. It just continues to hog the CPU until I relaunch it from the Force Quit dialog.
Anyone have any ideas as to what could be causing it, and what else I could check to find out what file is being accessed?
This is on a 500MHz Pismo with 384MB running 10.3.2