macOS Sierra freeze on iMac late 2009 using Safari

I had the same problem - it seems to be a problem with time machine. It doesn't occur at my MacBook Pro late 2012 when the external tm hard disk is unplugged.

I was using an early 2011 MacBook Pro without time machine connected when mine last froze. I think the last come to is a red herring unless the type of freeze was different in some way.

I want to ask why you guys did it for me, if not, I'll take the call through service management. 18: d0: 71: a7: 35: d3. I want to know why, 1 imac, 1macbook 1macbook 2013, 2016, Alienware dell, hp ... sony .... iphone7, iphone6 ​​.... accessories go by, a lot and improve my not all before. whole disk locked for months. thank you.

, I want to measure

ip6s three I am taking that, I sold ip7, imac and macbook 2013 'ip6 then

This is a user to user support forum. Rather than tacking an incomplete question onto an existing thread choose an area from this Sitemap that is most relevant to your issue and start a new topic. Post in plain text without altering fonts or colors. It is easier to read.

tt2

I have an iMac 27 late 2009, macOS Sierra and have the exact same issue as everybody else. Safari freezes hard when scrolling, the mouse pointer still moves but I can't activate anything. The iMac doesn't freeze immediately, but after some time. And the only solution is to do a hard reset.
I have never had this problem prior to macOS Sierra, and as it seems I'm not alone.

Let's hope Apple does something about this soon.

I also have a Mac mini 2010 with macos Sierra, but without any problems at all.

i don't use time machine and have this problem so i don't think it is related.

Ever since the last update yesterday, and indexing.... and building up new cache.

SO FAR no issues yet - & I can had dozens and dozens of tabs to browser - more like it was when it was best functioning... have not maxed out with super duper heavy usage - but I've added new tools that take up my resources and texting and everything running very smooth.

I would suggest everyone have at least one device to back up in time machine. STUFF HAPPENS.

If you do it daily weekly or monthly - it really does not take that much time.

This is what I did immediately after installing the update: I logged into a 2nd user account I use only for movies and videos. On that account there's only about 2 GB of data... I did have a immediate spinning wheel issue until AFTER indexing was over... Once complete, it was smooth so I popped over to my heavy user account and logged in - and after opening up all my programs and closing them, allowing them to get all cache settled out, which took maybe half an hour... SMOOTH Sailing.

Yes, I had this hope too...This weeks update does nothing. My 2014s expensive IMac still freezes and crashes.

I can add that one other issue (bug) that I had prior to the update actually has disappeared.

At the user login prior to the update 10.12.2, I had a terrible keyboard lag which also appeared with my macos Sierra install. I had to push each key several times before the key was registered as a keystroke. That seams to be gone now, knock on wood ;-).

A lot of my issues are gone.

I can still get it to spin and lock up if I open up a good number of tabs say 40-50 and especially when I have a good number of tabs open to search google images - that sets it off big time.

Safari seems to have sped up for me but still not as quick as many other browsers out there, and I do use a variety. For those wondering - the two 'Chrome' which I use not that often - theres a beta and the regular one many of you know.

I just installed the public beta of macOS Sierra 10.12.3 and the issue is still present. Computer freezes on late 2009 iMac, mouse still moves. Computer refuses to wake, black screen, mouse still moves. I'm thinking of rolling back to El Cap but I just noticed that my spouse's 2007 iMac also has a similar issue with freezing. Both machines have Samsung EVO SSDs installed thats the only common thing I can think of between the machines that could be causing an issue.

As both your machines have this issue and have an SSD installed and my machine has the issue (also with an SSD) I wonder if this isn't the common denominator of the problem. Maybe other people can chime in to detail if they have an SSD or spinning hard disk on their affected machines.