Benches macOS

9

Safari gives me the spinning wheel every …

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hello,

I've been having a ton of issues with Safari these past few weeks. I'm using version 3.2.1 (4524.27.1) and I've reset, trashed preferences, nuked fonts, run OnyX, repaired permissions... and I'm still having the same problems.

Basically after I've browsed for about 5 minutes, Safari will hang on whatever page I'm trying to load, whether I'm loading up pages in multiple tabs or just a single page. Sometimes I can get the page to finish loading and continue browsing if I hit "stop" and "reload" a bunch of times, but mostly I get the spinning beach ball wheel, and then Safari shows up as "not responding" in my Force Quit Applications window. The program doesn't crash - it just gives me the spinning ball until I have to force-quit, relaunch, and start over - only to do it all again.

It's driving me bonkers - I even had the cable company come out and check my cable modem connection (I'm using RoadRunner), but it was running normally.

Below is my console log from this morning, when I started up and had to force-quit Safari again. Hopefully the issue is really obvious and I can get back to normal:

-------

Mac OS X Version 10.4.11 (Build 8S165)

2008-12-03 09:53:44 -0500

2008-12-03 09:53:44.667 loginwindow[69] FSResolveAliasWithMountFlags returned err = -35

hidProduct=1095, storageProduct=1095,productName=iP6000D

InitHotplugNotification

USBAddNotifications

iP6000D

iP6000D

HIDDevice=1812800

HID Event usage = 0x0022, value = 0

HID Event usage = 0x0021, value = 0

HID Event usage = 0x0020, value = 0

2008-12-03 09:53:51.726 SystemUIServer[191] lang is:en

2008-12-03 09:53:57.235 SecurityFixer[220] No insecure startup items found!

Dec 3 09:53:57 Multiverse mDNSResponder: ReceivePortMapReply: response too short (12 bytes)

Dec 3 09:53:57 Multiverse mDNSResponder: ReceivePortMapReply: response too short (12 bytes)

Dec 3 09:53:58 Multiverse mDNSResponder: ReceivePortMapReply: response too short (12 bytes)

Dec 3 09:53:59 Multiverse mDNSResponder: NAT Port Mapping (LLQ event port.): timeout

2008-12-03 09:54:18.014 Translator[227] Invoked to sync conduit com.apple.Safari for entityNames: com.apple.bookmarks.Folder,com.apple.bookmarks.Bookmark

Debugger() was called!

Dec 3 10:14:56 Multiverse /Applications/Safari.app/Contents/MacOS/Safari: doClip: empty path.

Dec 3 10:14:56 Multiverse /Applications/Safari.app/Contents/MacOS/Safari: doClip: empty path.

Dec 3 10:14:56 Multiverse /Applications/Safari.app/Contents/MacOS/Safari: doClip: empty path.

Dec 3 10:14:56 Multiverse /Applications/Safari.app/Contents/MacOS/Safari: doClip: empty path.

Dec 3 10:14:56 Multiverse /Applications/Safari.app/Contents/MacOS/Safari: doClip: empty path.

2008-12-03 10:55:50.556 dotmacsyncclient[277]
* Assertion failure in -[SMSession _lockResourceAtPath:uploadPath:owner:failIfMissing:autoRenew:], /SourceCache/DotMacSyncManager/DotMacSyncManager-157/src/SMSession.m:2884

2008-12-03 10:56:20.558 dotmacsyncclient[277]
* Assertion failure in -[SMSession _lockResourceAtPath:uploadPath:owner:failIfMissing:autoRenew:], /SourceCache/DotMacSyncManager/DotMacSyncManager-157/src/SMSession.m:2884

2008-12-03 10:56:50.559 dotmacsyncclient[277]
* Assertion failure in -[SMSession _lockResourceAtPath:uploadPath:owner:failIfMissing:autoRenew:], /SourceCache/DotMacSyncManager/DotMacSyncManager-157/src/SMSession.m:2884

2008-12-03 10:57:20.561 dotmacsyncclient[277]
* Assertion failure in -[SMSession _lockResourceAtPath:uploadPath:owner:failIfMissing:autoRenew:], /SourceCache/DotMacSyncManager/DotMacSyncManager-157/src/SMSession.m:2884

9 replies

Sign in or join Beachball Help to reply.

  1. 0

    QuickTimeKirk

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    DNS (Domain Name Server) lookup issues.

    Search these Discussions pages for some possible fixes.

  2. 0

    gjanee

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Try turning off Safari's new anti-phishing feature: go to Preferences, Security pane, uncheck "Warn when visiting a fraudulent website". This has fixed the problem for me (so far).

    It occurred to me to try this because I only observed this behavior after upgrading to 3.2.1, and I noticed that the Preferences panel had a warning that the Google Safe Browsing feature was unavailable. I'm guessing that the Google known-bad-websites list that Safari contacts was down, and the browser would go into an infinite loop trying to contact it.

  3. 0

    Spyros Andreopoulos

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    To prevent Safari from crashing or no responding, Open Safari Preferences and replace it as your default browser with another browser as the default. In my case I have made FireFox my default browser in the Safari Preferences. Now Safari works like a charm, it starts when I open it, and quits without any problems.

    --Spyros

  4. 0

    Daniel Kanemoto

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi everyone -

    First off, thanks for all the suggestions. I've tried each one - unfortunately, Safari is still giving me the spinning wheel when I surf for more than a couple of minutes.

    Taking QuicktimeKirk's advice, I did a discussions search for "DNS issue" and found several threads that recommended adding OpenDNS DNS Servers to the Network preferences pane (208.67.222.222, 208.67.220.220). I also registered at the OpenDNS website and installed their "OpenDNS Updater" software.

    After I did this, Safari seemed to actually go to the spinning wheel, freeze-up state quicker... although I might be a bit paranoid.

    I forgot to mention that I already had "Warn when visiting a fraudulent website" checked off the in the preferences pane, and replacing Safari with Firefox as the default browser unfortunately didn't make much of a difference.

    I'm copying below my most recent Console log. Perhaps there's something different I need to do with DNS...? Quicktime Kirk, if you suspect it's something to do with DNS, could you please be more specific with regards to what I should be looking for? I really appreciate it.

    Thanks again for all the tips, everyone. I've got my fingers crossed that with your help, I'll be back to normal soon!

    ---------

    Mac OS X Version 10.4.11 (Build 8S165)

    2008-12-03 21:44:33 -0500

    2008-12-03 21:44:33.857 loginwindow[69] FSResolveAliasWithMountFlags returned err = -35

    hidProduct=1095, storageProduct=1095,productName=iP6000D

    InitHotplugNotification

    USBAddNotifications

    iP6000D

    iP6000D

    HIDDevice=1812800

    HID Event usage = 0x0022, value = 0

    HID Event usage = 0x0021, value = 0

    HID Event usage = 0x0020, value = 0

    2008-12-03 21:44:43.117 SystemUIServer[194] lang is:en

    2008-12-03 21:44:45.850 SecurityFixer[224] No insecure startup items found!

    Dec 3 21:44:46 Multiverse mDNSResponder: ReceivePortMapReply: response too short (12 bytes)

    Dec 3 21:44:46 Multiverse mDNSResponder: ReceivePortMapReply: response too short (12 bytes)

    Dec 3 21:44:46 Multiverse mDNSResponder: ReceivePortMapReply: response too short (12 bytes)

    Dec 3 21:44:47 Multiverse mDNSResponder: NAT Port Mapping (LLQ event port.): timeout

    2008-12-03 21:45:06.583 Translator[230] Invoked to sync conduit com.apple.Safari for entityNames: com.apple.bookmarks.Folder,com.apple.bookmarks.Bookmark

    Debugger() was called!

    Debugger() was called!

  5. 0

    Daniel Kanemoto

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi all -

    I tried using Safari on my computer after logging in as a different user, and it doesn't appear to freeze up. I'm hoping that info can help someone point me in the right direction towards solving my issue...?

    Should I post a crash report along with my console info? The last crash that's listed is dated from a month ago - the problem I'm having now is that it freezes up with the spinning wheel, which doesn't look like it's creating a crash report.

    Thanks -

    Dan

    was from a month ago - the problem I have right now is that it's

  6. 0

    Rogduckett

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi, Daniel -

    First of all, try not to get too frustrated about this problem, because you're not alone, and although no one has yet been able to track it directly to the new Safari 3.2 or 3.2.1 update, the problem seems to have arisen just after people updated their machines to these. Almost all the time, the problem is actually being caused by third-party add-ons, plug-ins, codecs, etc., or utility programs not following international standards, while Safari does.

    Questions:

    Does this problem occur when using any other browsers (Firefox, Camino, IE), or only with Safari?

    What type of internet connection are you using (wired to modem/router, wireless, dial-up, broadband, cable, etc.)

    There are several other threads discussing similar situations, and Klaus1 (for one) has posted a list of ideas/suggestions (from using OpenDNS servers, to deleting certain .plist files, to clearing Input Methods and InputManager folders, to clearing cache and history, to Repairing Permissions, and a few other actions) on many of these threads, which has fixed the problems for many people.

    It would be to your advantage to read some of those threads and try their suggestions, since they have worked for many users. Pay specific attention to posts by Klaus1, ~Bee, Mulder, nerowolfe, QuickTimeKirk, and Rachel R (and others whose IDs I forget).

    Don't give up - the volunteers on these forums are very knowledgeable, and will do their best to get you back on the road to being a happy camper. 🙂

    Good luck,

    Rog

  7. 0

    Klaus1

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Daniel!

    Try this:

    The following usually works on both Tiger and Leopard:

    (First, if yours is an Intel Mac, check that Safari is not running in Rosetta, which is enough to slow it to a crawl.)

    Many, including me, have had success with adding DNS codes to their Network Settings, with good results in terms of speed-up:

    Open System Preferences/Network. Double click on your connection type, or select it in the drop-down menu. Click on TCP/IP and in the box marked 'DNS Servers' enter the following two numbers:

    208.67.222.222

    208.67.220.220

    Click on Apply Now and close the window.

    Restart Safari, and repair permissions.

    If that didn't do it, then try this as well:

    Empty Safari's cache (from the Safari menu), then close Safari.

    Go to Home/Library/Safari and delete the following files:

    form values

    download.plist

    Then go to Home/Library/Preferences and delete

    com.apple.Safari.plist

    Repair permissions (in Disk Utility).

    Start up Safari again, and things should have improved.

  8. 0

    Christoff2

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I had suggested that users delete IPNetTunerX if they currently have it installed. At this point, I think it's an issue with plugins. I don't think it's a DNS server issue as I have had no problems with the other browsers. Try eliminating plugins that you don't need and check the flash players at
    http://www.adobe.com/shockwave/welcome/

    and at

    http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_15507

  9. 0

    Finalcutpro

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I had the "Google safe browsing is unavailable" on my iMac. I just went to disk utility and hit 'Repair Permissions." Now the message isn't there.