Error --> com.apple.Safari.History quit unexpectedly.

Hello folks,

for me work another work arround. I just go into the spotlight settings and uncheck the checkbox Bookmarks & History.

Works pretty good for me.

After that spotlight works normal again. I even apply this checkbox again! And there it is! Everything is normal and I even get all bookmark & hisory suggestions again.

Please cross check this! May it work also for another one of you guys!

Best regards & good luck!

I can confirm that removing the StagedFrameworks directory resolves the Spotlight crashing, but it borked Safari for me. Even relinking my dyld database with Tinkertool System didn't fix the problem. Luckily, the next day Mac App Store allowed me to reinstall the update...which of course brought back the bug.

At least that was easier than reinstalling my OS from a backup to fix Safari...

So I tried the Framework removal and found no joy. However, I might have work around for using Spotlight at least until Apple pulls whatever they have stuck up wherever it is stuck, and provide a real fix.

Just to be sure we've all on a similar page. With the most recent updates, whenever you open Spotlight and start to search, the Safari history error appears and spotlight closes, thus making spotlight useless. So try this;

As before, open spotlight start a search, get the error message and let spotlight crash (as if you have a choice) BUT instead on closing out the error box leave it open. RE launch and continue your search with sportlight. In my case I found spotlight would allow me to enter text and perform my searches.

I know this is a Hill-billy fix but, until those who are suppose to do their job and provide a working OS actually do that, its an option.

Good luck

OK, after just a little bit more directory-diving, here's what I SUSPECT is going on -- but I don't have time to test the theory and potentially messing up my system forever.

Assuming that the

System/Library/StagedFrameworks

Safari

System/Library/Frameworks

System/Library/PrivateFrameworks

There are some existing frameworks in those two directories that have newer versions within the

StagedFrameworks/Safari

directory --

Frameworks/JavaScriptCore.framework

PrivateFrameworks/Safari.framework

PrivateFrameworks/SafariShared.framework

PrivateFrameworks/WebInspector.framework

PrivateFrameworks/WebInspectorUI.framework

Frameworks/WebKit.framework

There are also two apparently new framework files:

WebCore.framework

WebKitLegacy.framework

I'm kind of curious whether or not these various files should have been copied off into the other directories prior to the installer updating the various dynamic library caches? Any ideas out there?

That seemed to do the trick.

1. Choose Apple Menu (top left corner of your screen), then System Preferences, then Spotlight

2. Disable "Bing Web Searches"

3. Disable "Bookmarks & History"

4. Close System Preferences

Sorry to hear that...just confirmed that Excel 2016 and a few other applications still launch fine for me without causing Spotlight-related Safari History crashes. Hopefully Apple fixes this bug soon!

Spotlight does not explicitly crash on my (very clean) install of El Capitan and I can still use Spotlight but there is a crash report in Console ("saved crash report for com.apple.Safari.History") every single time I invoke Spotlight with the keyboard. This happens regardless of changing these settings in Spotlight system preferences. This does not happen when searching using the Finder.

You need to delete the file com.apple.Safari.History.xpc.

The easiest why is to get the app EASY FIND (EXCELLENT, better than spotlight).

Looking for the file "com.apple.Safari.History.xpc"..

Easy find has a way where you can go direct to finder, and see this file.

Luiz

I believe this whole thread pertains to the recent update to El Cap. The issue does not happen with Sierra or at least Spotlight doesn't explicitly quit (and I am not yet up to speed with the new Console app in Sierra). This file, com.apple.Safari.History.xpc, is part of the system frameworks so I don't think it is a good idea to delete it. Interestingly on my El Cap system, there are two such files, one in PrivateFrameworks and one in StagedFrameworks, with different version numbers, 11601 and 11602, respectively.

Here is a less than elegant workaround.

Hope this does not dissuade Apple from fixing this silly, self-created issue.

1. When you start your day, do a Spotlight search. You will get the EEROR WINDOW. Some get 2 within a couple seconds.

2. Do not click IGNORE nor REPORT. LEAVE THAT ERROR BOX OPEN.

3. You can go back to Spotlight and do searches as long as you DO NOT CLICK on either option in the error box.

4. That will work until you shut down and start again. First search thereafter will fail again. Just ignore the box and you have a working Spotlight until ...

OK?

In my opinion, with this trend, Apple's fail will be even faster.

In the last 18 months I receive only disappointments from Apple - both hardware and software related.

I am stunned from their arrogance and lack of respect to my business and my money.

I was a big fan, now I try not to mention and not to recommend them anymore...

I have had the same issue as everyone else. the suggestion to leave the crash pop up box open after Spotlight crashes is a good one. I am keeping it up and moving it to a separate desktop so I don't have to look at it. Looking forward to a fix soon Apple.

Good.

But for the obvious, it would be amusing that the "crash box", which you and I move to the most distant corner of another desktop, always "stays on top" of all other open windows.

Now... Making that happen, takes talent.

Hi All,

I'll throw my hat in the ring as well to document one more system that this is impacting. I concur with all in this thread; the com.app.Safari.History keep unexpectedly crashing ALL THE TIME and it began after the most recent system update for El Capitan . I'll submit/open a ticket with apple to hopefully increase the priority of this issue. Debating re-installing an older version of El Capitan because I'm sick of this.

Colette: Sierra doesn't have this problem, but like many I am not updating to Sierra until all the documented problems with it, particularly with PDFs, have been fixed. I need my Mac to work reliably for work and apart from this Spotlight problem (that I can cope with as long as I use Steve Manning's workaround), it does. And I don't have any problems with PDFs that I use very extensively.