Thanks for the tip (the deactivation of the 'accelerated drawing components' within Safari), for my machine at least it seems to have done the trick!
Same issue. iMac freezing once or twice a day. I quit using Safari as that seemed to be the source of the issue and was confirmed by the forums full of the same Safari related problems. Started using Chrome exclusively. The freezing seemed to cease and then after a couple of months… the iMac freezes, mouse pointer functioning again, no force quit, system absolutely dead. A hard reboot was required on each occasion. I checked the hard drive, video card, mother board… all ticking along nicely. It had to be a software issue. I did notice the problem seemed to occur when iTunes and Chrome (especially when I was streaming content for iPlayer for example) were open together.… maybe a coincidence or my paranoia. It's been driving me insane for the past couple of months but lately was becoming a more regular issue (freezing 3-4 times a day) to extent that I was contemplating on retiring the 'old girl' and selling a kidney and buying a new one.
But no… another day another 'freeze' another reboot and a last but hopeful trawl through the forums to find a solution. An lo… the 'accelerated drawing components' deactivation. What the ****… I'll give it ago. And lo… it's been a day and half without a single 'freeze' (which is, in itself a bloody miracle!) and I've switched back to Safari (with some trepidation) but all is good so far. What I don't understand is why the 'system' as a whole seems to be working perfectly now by just this change? Maybe my complete lack of coding expertise or my decades old belief 'that it's a Mac, it just works' mantra still holds true… but which has been sorely tested of late.
I wouldn't normally post but this 'freezing issue' has been around for a while and I assumed that it had been addressed by the recent Sierra updates. Like a lot of people I'm clinging onto my 'antiquated' iMac for the sake of my bank balance until it explodes. To discover that it might be OS software issue (of which I've had my suspicions) and not my iMac makes it more galling that Apple have not even acknowledged or addressed the issue. Or maybe I've missed something! Anyhow thanks again… and to anyone with the same issue give it a go… you have nothing to lose except your sanity.
Spec: iMac (27-inch, Late 2009), 2.66 GHz Intel Core i5, 16 GB 1067 MHz DDR3, ATI Radeon HD 4850 512 MB, macOS Sierra Version 10.12.3