Safari crashing lately?
Published 4 years, 10 months ago in macintoshI’ve been having problems with Safari crashing a lot lately, and I had no idea why, until I read a post from RailHeadDesign (no permalink, so I’ve quoted in full here):
Safari Been Eating CPU Cycles Lately?
Last month I started noticing Safari suddenly locking-up, taking 75% to 130% of my processor(s), constantly needing to be force-quit. The first symptoms presented themselves when I would load several sites at once (by command-clicking a bookmark folder in the toolbar). The sites would attempt to load, but then everything would just stall and Safari would eventually throw-up the spinning beach ball we all know and love. I then noticed, using iPulse and the Terminal’s “top” command, that Safari was eating processor cycles when this was happening.I tried all manner of things to correct the issue, and I jumped into a thread at Apple’s message boards where others were experiencing the same thing. Within a couple of days, we seem to have found the problem that was causing Safari to ‘freak out’ on us: third-party applications that (seemingly) do a poor job of accessing certain features of Apple’s web kit.
In my case, the application that seems to have been causing problems was NetNewsWire v1.0.4 , released August 25/26 ‘ coincidentally when the symptoms first started showing themselves. One of the features of this version of NNW was ‘NetNewsWire now uses Web Kit, Safari’s HTML renderer.’ Hmm’
Just yesterday, Ranchero released v1.0.5b1 of NetNewsWire , and one of the changes listed is ‘Don’t share cookies with Safari anymore ‘ this fixes a couple crashes and fixes some hangs.’ Since upgrading to the latest beta, all my Safari freak-out problems have gone away. Users of other news readers are reporting the same issues, but I haven’t heard anything back yet.
The bottom line is this: Safari was becoming totally unusable, and became that way when NetNewsWire v1.0.4 was released. Ranchero made v1.0.5b1 available, which no longer shared cookies with Safari (through the web kit, I think), and the Safari issues went away. There’s obviously a link there somewhere, and any other third-party application that is sharing information with Safari could also cause potential Safari issues.
So, if you’re experiencing Safari hang issues like I was, and you use NNW, download the latest beta.
4 Responses to “Safari crashing lately?”
Leave a Reply
Search
Subscribe
Archives
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003
- August 2003
- July 2003
- June 2003
- May 2003
- April 2003
- March 2003
- February 2003
- January 2003
- December 2002
- November 2002
- October 2002
- September 2002
- August 2002
- May 2002
Categories
- asides (422)
- baby (6)
- design + dev (142)
- for sale (7)
- get a job (11)
- investing (6)
- leadership + management (145)
- life stories (250)
- macintosh (320)
- marketing + advertising (223)
- Moveable Type (52)
- organization (6)
- photography + video (68)
- publishing + content (136)
- random (222)
- Saab (1)
- sales and selling (93)
- small business (147)
- stuff (67)
- sysadmin (40)
- travel (42)
- Video (2)
- windows (69)
- WordPress (13)
Yup, this is exactly what was happening to me — Safari was suddenly the Force Quit king of my iBook. Then I read about the beta release in (of course) NNW, and realized that I almost always have NNW and Safari running at the same time. 2+2. Tomorrow will be the first time I have the beta and Safari both running for the full day, so we’ll see if indeed that’s the fix
Man I’m glad you posted this. I’ve been so pissed at my computer lately, and this is the problem. I’ll be loading the beta asap.
Me too, same thing. I was getting pissed, because I always use the two together. When I saw the remarks from Ranchero, I knew that was the problem. No issues with Safari since upgrading to the beta of NNW.
I’m not using NNW, but I’m sure Safari is not playing well with something I’ve got loaded. I’ve been getting these same issues the last few days…at least since updating to Safari’s latest version.