My Current Set up is as follows in case this makes any Difference:
24" Imac with 2.8GHz Extreme C2D.
2 GIG Ram (Standard)
OS X 10.5.2 Fresh Install, Fully Updated and only handful of added Apps.
I have attached a Picture of what happens randomly when using the FAN View on any Folder on the Dock. At first I thought it was the machine had too much Crap on there so recently I rebuilt it from Scratch. The iMac Came with 10.4.X x 2 CD/DVD and a Leopard Update DVD. To make sure that no added application or plug-ins were at fault, I made sure that only only installed the very basic's of what I needed.
Now I put the machine to Sleep at the end of each Session and not shut it down and this may have something to do with it, it effects Any folder put on the dock in fan View and cannot re-create at will but randomly happens.
My Guess is iChat - I notice after chatting to people on that, it starts to happen - If I do not run iChat for a week at a time, no corruption seems to occur. Anybody any idea why this happens, does anybody else have this problem? Is this just a 10.5.2 bug which maybe gets fixed later?
24" Imac with 2.8GHz Extreme C2D.
2 GIG Ram (Standard)
OS X 10.5.2 Fresh Install, Fully Updated and only handful of added Apps.
I have attached a Picture of what happens randomly when using the FAN View on any Folder on the Dock. At first I thought it was the machine had too much Crap on there so recently I rebuilt it from Scratch. The iMac Came with 10.4.X x 2 CD/DVD and a Leopard Update DVD. To make sure that no added application or plug-ins were at fault, I made sure that only only installed the very basic's of what I needed.
Now I put the machine to Sleep at the end of each Session and not shut it down and this may have something to do with it, it effects Any folder put on the dock in fan View and cannot re-create at will but randomly happens.
My Guess is iChat - I notice after chatting to people on that, it starts to happen - If I do not run iChat for a week at a time, no corruption seems to occur. Anybody any idea why this happens, does anybody else have this problem? Is this just a 10.5.2 bug which maybe gets fixed later?