Snow Leopard / Safari

Discussion in 'macOS' started by stordoff, Aug 29, 2009.

  1. stordoff macrumors regular

    Aug 24, 2009
    Since upgrading to SL, Safari has been hanging (beachball cursor) all the time, causing the whole system to run painfully slow. Console shows the following (extract). Any ideas?

    2009-08-29 12:05:11[1241] Debugger() was called!
    2009-08-29 12:10:05[1241] Debugger() was called!
    2009-08-29 12:10:18[1241] Debugger() was called!
    2009-08-29 12:12:47[1241] Debugger() was called!
    2009-08-29 12:14:23[1241] Debugger() was called!
    2009-08-29 12:15:31[1241] Debugger() was called!
    2009-08-29 12:15:45[1241] Debugger() was called!
    2009-08-29 12:32:03 UserEventAgent[111] **** ERROR: SCNetworkSignatureCopyActiveIdentifiers returned nil
    2009-08-29 12:32:13 [0x0-0xff0ff].SoftwareUpdateCheck[1363] SoftwareUpdateCheck: network unreachable
    2009-08-29 12:32:13[1] ([1364]) Exited with exit code: 2
    2009-08-29 12:32:13[89] ([0x0-0xff0ff].SoftwareUpdateCheck[1363]) Exited with exit code: 3
    2009-08-29 12:58:27[1241] Debugger() was called!
    2009-08-29 12:58:35[1241] Debugger() was called!
    2009-08-29 12:58:55[1241] Debugger() was called!
    2009-08-29 12:59:03[1241] Debugger() was called!
    2009-08-29 13:01:06[1241] Debugger() was called!
    2009-08-29 13:01:22[1241] Debugger() was called!
    2009-08-29 13:03:02[1241] Debugger() was called!
    2009-08-29 13:04:07[1241] Debugger() was called!
    2009-08-29 13:08:38[1241] Debugger() was called!
    2009-08-29 13:16:08[1241] Debugger() was called!
    2009-08-29 13:17:17[1241] Debugger() was called!
    2009-08-29 13:34:20[1241] Debugger() was called!
    2009-08-29 13:34:54[1241] Debugger() was called!
    2009-08-29 13:36:50[1241] Debugger() was called!
    2009-08-29 13:41:15[1241] Debugger() was called!
    2009-08-29 13:42:19[1241] Debugger() was called!
    2009-08-29 13:49:12[1241] Debugger() was called!
    2009-08-29 13:49:39[1241] Debugger() was called!
  2. kainjow Moderator emeritus


    Jun 15, 2000
    You could try these:
    - Reset Safari (clears cache, cookies, etc)
    - Remove all Safari preference files
  3. stordoff thread starter macrumors regular

    Aug 24, 2009
    Thanks. I've reset Safari. How do I do about clearing preference files?

    I have noticed it seems to happen more when a flash-heavy page is open and I open a new tab. Could this be a problem with flash, rather than Safari?
  4. MarcBook macrumors 6502a


    Jul 13, 2008
    United Kingdom
    I've noticed that Flash Player uses a lot more CPU power in Snow Leopard than in Leopard. The issue could be causing more beach balls...

    I updated to the latest version of Flash Player (apparently Snow Leopard's pre-installed version is out-of-date?) and it seemed to help a tiny bit... Not much though.

    Flash Player comes up as a separate process in Activity Monitor, so it's worth having a look at how much CPU it's taking when active (YouTube high quality videos are a good test).

    I hope Adobe gets a move on and improves their Mac plug-in. It's been ages now and it's still awful.
  5. kainjow Moderator emeritus


    Jun 15, 2000
  6. entwife macrumors regular

    Feb 17, 2008
    Im also getting loads of random lines streaking across the screen when i initially load a web page (almost like a barcode), anyone else getting this??

    it only lasts a few seconds but is annoying
  7. stordoff thread starter macrumors regular

    Aug 24, 2009
    I'm updating Flash now. A single tab open playing a HQ YouTube video takes ~70% of my processor and masses of memory (real and virtual). Going to HD takes ~105% processor.

    Edit: I've updated Flash. It still uses ~70% for a single HQ video. However, I can now have lots (I tried 6) HD YouTube videos playing, and CPU usage didn't go over 100%. Also, no more beachballs (Opening loads of tabs was a sure fire trigger before, works fine now)

    Thanks Guys
  8. kainjow Moderator emeritus


    Jun 15, 2000
    SL did introduce a new "safer" method of handling plugins in WebKit. The plugins are in a separate process so if the plugin crashes, it doesn't take down the entire app (Safari). Sounds like they still have some kinks to work out...
  9. IBradMac macrumors 68000


    Jun 27, 2008
    You aren't the only one.. I just checked my console and got this;

    9/1/09 9:55:27 PM[6905] Debugger() was called!

    I got this message like 5 times. Anyone know what it means?
  10. dknepprath macrumors newbie

    Sep 2, 2009
    I'm having the random lines as well as the beach ball since updating to SL. Hopefully they release an update to resolve this soon.

    I was having major beach ball every time I opened a new tab. Disabling Top Sites resolved this, but that is not a very pleasant work-around. I have come to love my Top Sites!
  11. Macula macrumors 6502


    Oct 23, 2006
    All over the place
    +1 for the random lines.
  12. sectionsix macrumors newbie


    Sep 3, 2009
    I too have noticed that Safari and the latest version of Webkit us a lot more CPU when watching flash videos on youtube or any other other flash video site since the update to SL. I'm not sure if it's just my imagination but, forcing Safari and/or Webkit to run in 32 bit mode seems to have helped the CPU spiking.
  13. lewiguez macrumors newbie


    Oct 10, 2008
    Akron, OH
  14. Silentwave macrumors 68000

    May 26, 2006
    Gainesville, FL
    I had the beachballs to the point where Safari would completely freeze and had to be killed.

    I tracked it down to Flash.The thing is, it started *after* I updated to the latest version per the security advice.

    Older versions of flash don't seem to help, only either completely uninstalling it or using ClickToFlash so that none of the flash loads unless I say so. Even then, as soon as I try, it crashes.

    So far this only seems to be affecting my Mac Pro, but I haven't updated flash on my MBP and don't intend to until the next release.
  15. cameronfield macrumors member

    Aug 11, 2009
    Hey guys, I had a similar problem a few days ago and a fellow member helped me out and I'm beachball free -->

    Now my safari wasn't completely locking up, just beachball for 30 seconds solid every 5 mins or so.

    13" July MBP
    Snow Leopard (upgrade, not clean)
    Newest flash
    Newest safari

    Since following his tips I haven't gotten a single beach ball.

    Hope this helps!

Share This Page