This is a bit of a long shot, I guess, but I'm writing a utility (in Objective-C) that tidies up my desktop automatically for me. It's all going fine; I use the pretty neat Scripting Bridge framework to communicate with the Finder to get and set positions of icons on the desktop, and whilst the programme is running, all is well. However, when I quit it I have noticed that Finder will all of a sudden no longer be idling on 0.x percent of CPU usage, but at a rate that seems to be proportional to the amount of use my app has had. I.e, if I've been testing it heavily, when I finish Finder can be idling as much as 80% of CPU (on a dual core iMac, so that's only 40% of what's available of course). Also I've had a couple of alarming crashes as well which seem to have been caused by the Finder, during which attempts to force quit applications fail, the force quit dialogue box is displayed empty until eventually nothing works (the Title Bar tells me Finder is continually active all the time, and is in fact responsive) and I have to do a hard reset. So, if anyone has had any experience of anything similar and maybe if there's something I should be thinking about (I'm pretty sure by now I'm releasing all my references to the SBElementArrays I'm using properly, but you never know), then that would be very helpful. Otherwise I may send some Finder traces to Apple and just leave it at that. Will be annoying if I can't actually use my app in the end. Thanks, David EDIT: Should have mentioned I'm running 10.6.2 and it's a 2.4 GHz C2D 2008 20" Alu iMac. No dodgy external hardware attached, as well, and no kernel panics.