Monday, March 18, 2013 [Tweets] [Favorites]

Safari Still Craps Out Too Frequently

Erik Barzeski:

Seriously, it’s 2013. I have 32 GB of RAM. And Safari still craps out all the time and has to reload every page I’ve loaded with as few as 20 tabs open.

Ever since the Safari Web Content process was split off in Lion and sandboxed (the Safari application remains unsandboxed), I’ve been getting into situations where pages stop responding until I quit and relaunch Safari.

4 Comments

"Ever since the Safari Web Content process was split off in Lion and sandboxed (the Safari application remains unsandboxed), I’ve been getting into situations where pages stop responding until I quit and relaunch Safari."

Safari 5.0.5 still runs like a champ. I avoided the supplemental updates to 10.6.8 precisely to avoid downgrading Safari to the Lion model.

[...] two dimensions to one. Xcode and other apps have become less AppleScriptable. Safari has become buggy. Changes to Sync Services, without adequate replacements, broke Outlook and Yojimbo. Some things [...]

[...] Alas, though Chrome and Firefox have good rendering engines, they do not have fully native Mac user interfaces. Safari has both, but its engine has reliability and memory problems. [...]

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment