This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.

Safari 6 crashing on Mountain Lion

dteare
dteare Agile Founder
edited February 2013 in Knowledge Base & FAQs

IMPORTANT: Apple has resolved this issue in OS X 10.8.1 along with many other improvements. We encourage you to update Mountain Lion to the latest version rather than trying to work around a problem that has already been fixed.

Update Mountain Lion

This support article only pertains to Safari 6 on the old version of Mountain Lion 10.8.0. If Safari 6 is not crashing or you are running the 10.8.1 update, this support article does not apply to your situation.

We were disheartened to learn that in rare cases Safari 6 was constantly crashing for some of our awesome customers. In our investigation so far, we have found this was a bug in OS X 10.8.0 related to proxy settings. This affects the 1Password extension due to the method we use to connect to the 1Password Helper from the Safari extension.

(Japanese version of this article: 日本の)

How To Resolve

  1. Update to OS X 10.8.1 as described at the top of this article.
  2. There is no step two.

If you are unable to update to OS X 10.8.1 for any reason, please read on.

To quickly resolve this crashing issue in OS X 10.8.0, UNCHECK the “Auto Proxy Discovery” option in System Preferences > Network > Advanced > Proxies.

Disable Auto Proxy Discovery

Detailed instructions (with more screenshots) are available as well. Additionally, some customers have confirmed that turning off “Automatic Proxy Configuration” resolves the issue if “Auto Proxy Discovery” is already disabled.

Many users who do require a proxy server have worked around the issue by disabling “Automatic Proxy Configuration” and instead manually specifying HTTP and HTTPS proxies.

If you are unable to disable the above options and/or manually configure a proxy, you will need to remove the 1Password extension from Safari and use 1Password in either Chrome and Firefox until Apple resolves this or we can release an update to work around it as quickly as possible.

Geeky Details

If the above workaround doesn't solve the issue for you, your issue may be unrelated. Check the stack trace to be sure. Daniel Jalkut of Red Sweater Software has one of the best write-ups on the issue. In it he says:

The tell-tale sign of this crash is it occurs only as the app attempts to connect to some network resource, and the crashing thread always culminates in some stack trace involving CoreSchedulingSet or EmptyCoreSchedulingSet C++ objects.

If you have no idea what the above means or you are still having trouble even after updating to OS X 10.8.1, please start a new thread so we can help you get 1Password back up and running.