Current Position:Home > Beach Balls and freezes after installing Safari 3.1 and security update

Beach Balls and freezes after installing Safari 3.1 and security update

Update:10-11Source: network consolidation
Advertisement
Hi,
I just recently installed the safari 3.1 update and the security update. My machine is an iMac 2.4 GHz with 10.5.2. Prior to this, the machine only had one freeze (had to power off) which happened a about a month back. Since the update, 2 days ago, the machine seems to show the beach ball more often. On one specific occasion (happened when my son was using it), the Chess game was running, and the mouse cursor turned into a beach ball and everything froze - can only move the mouse cursor/beach ball but nothing else responded. Even hitting the caps lock key took minutes before the caps lock light came on. Me being a windows user for a long time, I was blindly trying to find the keyboard equivalent of ctrl-alt-del to pull up a process list of some kind so that I can kill the offending app. But was not successful, hence I had to power off.
On another occasion, and this time, it happened to me - the beach ball came up as I was using safari. I could use other stuff in the OS, but any time I brought the cursor over safari, it would turn into a beach ball. After waiting a few minutes and clicking away on the safari window, the beach ball turned into a finger cursor when I clicked on the http address window - and safari started to work like normal again.
I'm wondering if anyone else has had experiences similar to this and if there are any steps I can take to prevent this again.
Thanks in advance.

The Best Answer

Advertisement
Welcome to the Apple forums:
Did you perform both updates at the same time? I usually recommend doing them one-at-a-time, so if anything happens you know which update caused the problem.
I especially never do a system update with any other update. I always do that one last, and wait for the dust to settle by reading this board first.
You should run DU and check the HD and repair permissions. That's a start.