Safari crashes immediately after I open it. This started today, and happens 100% of the time. The error message says "Safari Web Content Quit Unexpectedly." I'm using a Macbook Pro, Mid-2012, 2.5 GHz Intel Core i5, 8 GB memory, Yosemite 10.10.3. I'll post the error report shortly.
MacBook Pro, OS X Yosemite (10.10.3)
Hi. Take a look at this article: Unsupported third-party add-ons may cause Safari to unexpectedly quit or have performance issues - Apple Support
Try launching Safari while holding down the shift key and post the crash message here if the issue persists
Holding the shift key didn't help. I'm trying to copy and paste the error report now. For some reason every time I hit the "reply" or "post" button when pasting the report, nothing happens.
Process: com.apple.WebKit.WebContent [4574]
Path: /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/XPCServices /com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent
Identifier: com.apple.WebKit.WebContent
Version: 10600 (10600.6.3)
Build Info: WebKit2-7600006003000000~2
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Safari [3684]
User ID: 501
Date/Time: 2015-06-09 10:58:40.884 -0400
OS Version: Mac OS X 10.10.3 (14D136)
Report Version: 11
Anonymous UUID: FE2E8510-9246-509D-805D-351B9E555434
Sleep/Wake UUID: 8F84DD20-C0D1-40FB-B38F-484BF62766D1
Time Awake Since Boot: 24000 seconds
Time Since Wake: 7500 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000112797800
VM Regions Near 0x112797800:
WebKit Malloc 0000000112773000-0000000112775000 [ 8K] ---/rwx SM=NUL
--> WebKit Malloc 0000000112775000-00000001127b5000 [ 256K] rw-/rwx SM=COW
WebKit Malloc 00000001127b5000-00000001127b7000 [ 8K] ---/rwx SM=NUL
Application Specific Information:
Bundle controller class:
BrowserBundleController
Process Model:
Multiple Web Processes
Please post the whole crash report. If you can't post it here, post it on pastebin.com and post a link here to the page you created.
Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Please take this step regardless of the results of Step 1.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.
Short Followup: Safari is now working on all accounts.
What I Did: I went through Step 1 of your test. When I signed in on the guest account, Safari was not working (but that may be because there is a possibility that Find My Mac is installed on my computer). Then I created a new user account and set it up as an admin. In order to set it up as an admin, I had to do a restart. After restarting and signing in with the new user account, Safari began working normally. I then signed in with my account, and Safari began working fine. I'm not sure why it started working. Maybe it was the restart (but I already restarted once this morning).
Safari Crashes Immediately After Opening
