rryoder

Q: Safari crashing each time I open it.

I'm using Safari 8.0.5 on a MacBook Pro mid-2012 with Yosemite 10.10.3, 2.5 Ghz, 8 GB Memory. Internal SSD. I installed Yosemite first when it became available last fall. Sometime soon after that, I noticed that Safari would often crash when I opened it, but would usually open fine when I tried a second or third time. This has gone on for 6-8 months. I work at a college with a Secure server, so attributed many of the issues I've had to that, but I've been home for the summer exclusively for over a month with the same problems.  BTW, Firefox and Chrome worked fine when starting and rarely if ever crashed in any setting I was using.

 

At the same time I've had a new onset, but ongoing problem with PowerPoint Tables, which means that when I put my cursor anywhere in a table and drag to select text, the application freezes and must be force quitted. I've been trying to run through some troubleshooting items for that for the past week working with someone on a Microsoft discussion board. That is not a main concern, but it lead to today's ramp-up of problems with Safari. In going through a troubleshooting step for the PPT problem, I restarted the computer in Safe Boot mode and evaluated if I had the same problem with PPT that I had without. It still happened.

 

When I returned to regular mode by restarting the computer, NOW Safari won't open at all. It has crashed on opening up to 10 times in a row. In trying to get online, I also tried Firefox and Chrome. Both of those are also not working. To get here to post this, I went back and restarted in Safe Mode. From there, I'm able to open Safari.

 

I tried to copy my crash report, but of course, it wouldn't survive a restart and I didn't paste it in another document. I only have two plug-ins listed at this point: 1Password and AdBlock. I can go back and copy the crash report if that is necessary.

MacBook Pro (13-inch Mid 2012), OS X Yosemite (10.10.3)

Posted on Jun 27, 2015 1:23 PM

Close

Q: Safari crashing each time I open it.

  • All replies
  • Helpful answers

  • by Eric Root,

    Eric Root Eric Root Jun 27, 2015 1:36 PM in response to rryoder
    Level 9 (73,337 points)
    iTunes
    Jun 27, 2015 1:36 PM in response to rryoder

    Safari/Preferences/Advanced - enable the Develop menu, then go there and Empty Caches. Quit/reopen Safari and test. Then try Safari/History/Show History and delete all history items.  Quit/reopen Safari and test. You can also try try Safari/Clear History and Web Site Data. The down side is it clears all cookies.Doing this may cause some sites to no longer recognize your computer as one that has visited the web site. Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J.  When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder.  Select Library./Caches/com.apple.Safari/Caches.db and move it to the trash.

     

    Go to Safari Preferences/Extensions and turn all extensions off. Test. If okay, turn the extensions on one by one until you figure out what extension is causing the problem.

     

    Safari Corruption       See post by Linc Davis


  • by Linc Davis,

    Linc Davis Linc Davis Jun 27, 2015 1:56 PM in response to rryoder
    Level 10 (208,017 points)
    Applications
    Jun 27, 2015 1:56 PM in response to rryoder

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Step 1

    For this step, the title of the Console window should be All Messages. If it isn't, select

              SYSTEM LOG QUERIES â–¹ All Messages

    from the log list on the left. If you don't see that list, select

              View â–¹ Show Log List

    from the menu bar at the top of the screen.

    In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

    Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    Please don't indiscriminately dump thousands of lines from the log into this discussion.

    Please don't post screenshots of log messages—post the text.

    Some private information, such as your name, may appear in the log. Anonymize before posting.

    Step 2

    In the Console window, select

              DIAGNOSTIC AND USAGE INFORMATION â–¹ User Diagnostic Reports

    (not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

    I know the report is long, maybe several hundred lines. Please post all of it anyway.

    If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

    Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

    When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

  • by rryoder,

    rryoder rryoder Jun 27, 2015 2:45 PM in response to Linc Davis
    Level 1 (4 points)
    Apple Watch
    Jun 27, 2015 2:45 PM in response to Linc Davis

    These are the Console Messages:

    6/27/15 4:35:19.000 PM kernel[0]: Sandbox: com.apple.Safari(423) deny file-issue-extension /Users/~/Library/Caches/com.apple.Safari.SearchHelper

    6/27/15 4:35:19.620 PM com.apple.Safari.SearchHelper[423]: Failed to obtain sandbox extension for path=/Users/~/Library/Caches/com.apple.Safari.SearchHelper. Errno:1

    6/27/15 4:35:19.000 PM kernel[0]: Sandbox: com.apple.Safari(423) deny file-issue-extension /Users/~/Library/Caches/com.apple.Safari.SearchHelper

    6/27/15 4:35:19.621 PM com.apple.Safari.SearchHelper[423]: Failed to obtain sandbox extension for path=/Users/~/Library/Caches/com.apple.Safari.SearchHelper. Errno:1

    6/27/15 4:35:19.000 PM kernel[0]: Sandbox: com.apple.Safari(423) deny file-read-data /Library/Preferences/com.apple.security-common.plist

     

    This is the last Safari Crash log from the User Diagnostic Reports:

    Process:               Safari [899]

    Path:                  /Applications/Safari.app/Contents/MacOS/Safari

    Identifier:            com.apple.Safari

    Responsible:           Safari [899]

        __TEXT                  [    4K] r-x/rwx SM=COW  /Applications/Safari.app/Contents/MacOS/Safari

    com.agilebits.onepassword4-safari-2BUA8C4S2C (4030190 - 4.3.1) 1Password

    com.betafish.adblockforsafari-UAMUU4S2D9 (102.35 - 2.35) AdBlock

    Thread 0:: Dispatch queue: com.apple.SafariShared.WBSHistory.entriesByURLString

    1   com.apple.Safari.framework     0x000000010a498f6b ___ZNK6Safari18TopSitesController24computeTopSiteCandidatesERN3***6VectorINS_16 TopSiteCandidateELm0ENS1_15CrashOnOverflowEEE_block_invoke + 29

    2   com.apple.Safari.framework     0x000000010a6bc9b8 __39-[WBSHistory enumerateItemsUsingBlock:]_block_invoke_2 + 14

    5   com.apple.Safari.framework     0x000000010a6bc981 __39-[WBSHistory enumerateItemsUsingBlock:]_block_invoke + 105

    8   com.apple.Safari.framework     0x000000010a6bc8f3 -[WBSHistory enumerateItemsUsingBlock:] + 127

    9   com.apple.Safari.framework     0x000000010a33a6e5 -[History enumerateItemsUsingBlock:] + 39

    10  com.apple.Safari.framework     0x000000010a498c02 Safari::TopSitesController::computeTopSiteCandidates(***::Vector<Safari::TopSit eCandidate, 0ul, ***::CrashOnOverflow>&) const + 178

    11  com.apple.Safari.framework     0x000000010a49687c Safari::TopSitesController::updateFrequentlyVisitedNonBannedSites() + 72

    12  com.apple.Safari.framework     0x000000010a49520c ___ZN6Safari18TopSitesControllerC2Ev_block_invoke_4 + 13

    17  com.apple.Safari.framework     0x000000010a6bed72 -[WBSHistory _sendNotification:withItems:] + 212

    18  com.apple.Safari.framework     0x000000010a6bee7d -[WBSHistory _dispatchHistoryItemsLoaded:] + 30

    19  com.apple.Safari.framework     0x000000010a6be730 -[WBSHistory historyLoader:didLoadItems:discardedItems:stringsForUserTypeDomainExpansion:] + 469

    20  com.apple.Safari.framework     0x000000010a6d03ab -[WBSHistorySQLiteStore _finishLoadingOnMainThread] + 94

    32  com.apple.Safari.framework     0x000000010a167970 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246

    37  com.apple.Safari.framework     0x000000010a106f97 safari_NSButtonCell_trackMouse(objc_object*, objc_selector*, NSEvent*, CGRect, NSView*, signed char) + 175

    42  com.apple.Safari.framework     0x000000010a166f56 -[BrowserApplication sendEvent:] + 512

    60  com.apple.Safari.framework     0x000000010a167970 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246

    Thread 18:: Safari: WBSParsecSearchClient location

    5   com.apple.Safari.framework     0x000000010a6f2d6e -[WBSParsecSearchClient _locationThread] + 43

           0x10a0e4000 -        0x10a0e4fff  com.apple.Safari (8.0.5 - 10600.5.17) <E87842F8-F207-3F85-BA62-644CCE273825> /Applications/Safari.app/Contents/MacOS/Safari

           0x10a0f0000 -        0x10aa4dfff  com.apple.Safari.framework (10600 - 10600.5.17) <83AB27C4-CD1B-31FB-91C3-23E9CEC124F9> /System/Library/PrivateFrameworks/Safari.framework/Versions/A/Safari

           0x11d8b4000 -        0x11d8b6ff3  com.apple.SafariServices.framework (10600 - 10600.5.17) <55E7D2A9-802C-36E9-9D38-A2D34107740D> /System/Library/PrivateFrameworks/SafariServices.framework/Versions/A/SafariSer vices

  • by rryoder,

    rryoder rryoder Jun 27, 2015 3:29 PM in response to Kappy
    Level 1 (4 points)
    Apple Watch
    Jun 27, 2015 3:29 PM in response to Kappy

    Thanks, Kappy. I tried all of these, but they didn't make a difference.

  • by Linc Davis,

    Linc Davis Linc Davis Jun 27, 2015 3:45 PM in response to rryoder
    Level 10 (208,017 points)
    Applications
    Jun 27, 2015 3:45 PM in response to rryoder

    That's not a complete crash report. There should be at least one that's much longer, several hundred lines.

  • by rryoder,

    rryoder rryoder Jun 27, 2015 5:13 PM in response to Linc Davis
    Level 1 (4 points)
    Apple Watch
    Jun 27, 2015 5:13 PM in response to Linc Davis

    The one I saved in TextEdit from the Safari report was longer, but that was the longest one I found on Console. Would you like the one I got from Safari?

  • by rryoder,

    rryoder rryoder Jun 27, 2015 5:16 PM in response to Eric Root
    Level 1 (4 points)
    Apple Watch
    Jun 27, 2015 5:16 PM in response to Eric Root

    Thanks, Eric. I did all this except to delete the history items (I hate to lose that if I don't have to. These actions did not have an effect. Thanks!

  • by rryoder,

    rryoder rryoder Jun 27, 2015 5:28 PM in response to Linc Davis
    Level 1 (4 points)
    Apple Watch
    Jun 27, 2015 5:28 PM in response to Linc Davis

    Couldn't paste the Safari Crash log here for whatever reason. Here is a link to Pastebin.  http://pastebin.com/tRVSqrNU

  • by Linc Davis,

    Linc Davis Linc Davis Jun 27, 2015 5:31 PM in response to rryoder
    Level 10 (208,017 points)
    Applications
    Jun 27, 2015 5:31 PM in response to rryoder

    If Safari crashes on launch and you don't have another web browser, you should be able to launch Safari by starting up in safe mode.

    You may have installed the "Genieo" or "InstallMac" ad-injection malware. Follow the instructions on this Apple Support page to remove it.

    Back up all data before proceeding.

    Malware is always changing to get around the defenses against it. In addition to the files listed in the support article, you may also have some of the following:

    ~/Library/LaunchAgents/com.Installer.completer.download.plist
    ~/Library/LaunchAgents/com.Installer.completer.ltvbit.plist
    ~/Library/LaunchAgents/com.Installer.completer.update.plist
    ~/Library/LaunchAgents/com.spigot.SearchProtection.plist
    ~/Library/Application Support/IM.Installer

    Removing these files, if they exist, is optional if you've already followed Apple's instructions.

    One of the steps in the article is to remove malicious Safari extensions. Do the equivalent in the Chrome and Firefox browsers, if you use either of those.

    After removing the malware, remember to reset your home page in all the web browsers affected, if it was changed.

    If you don't find any of the files or extensions listed, or if removing them doesn't stop the ad injection, then you may have one of the other kinds of adware covered by the support article. Follow the rest of the instructions in the article.

    If you find Apple's instructions too hard to follow, ask for an alternative that doesn't require you to trust a black-box application without knowing what it does.

    Make sure you don't repeat the mistake that led you to install the malware. Chances are you got it from an Internet cesspit such as "Softonic," "CNET Download," or "SourceForge." Never visit any of those sites again. You might also have downloaded it from an ad in a page on some other site. The ad would probably have included a large green button labeled "Download" or "Download Now" in white letters. The button is designed to confuse people who intend to download something else on the same page. If you ever download a file that isn't obviously what you expected, delete it immediately.

    In the Security & Privacy pane of System Preferences, select the General tab. The radio button marked Anywhere  should not be selected. If it is, click the lock icon to unlock the settings, then select one of the other buttons. After that, don't ignore a warning that you are about to run or install an application from an unknown developer.

    Still in System Preferences, open the App Store or Software Update pane and check the box marked

              Install system data files and security updates (OS X 10.10 or later)

    or

              Download updates automatically (OS X 10.9 or earlier)

    if it's not already checked.

  • by rryoder,

    rryoder rryoder Jun 27, 2015 8:29 PM in response to Linc Davis
    Level 1 (4 points)
    Apple Watch
    Jun 27, 2015 8:29 PM in response to Linc Davis

    OK, I went through all of these files that you listed and on the Apple site. Found none of the specific ones listed, but I did find some with the endings listed for Sophos, Google keystone, Citrix Go to Meeting and a Coupon program that I had intentionally installed (all but Google Keystone???). I deleted all these program files because I don't need/use them any more and may have already deleted the programs anyway. Now I can log in to Safari, Firefox, and Chrome without any of them crashing. I don't understand why any of these intentional programs would have caused the problem, but I think it is now fixed!!! Thanks so much for all the help.