Am I hacked? EXC_CRASH (SIGABRT)

I was in my bank and was watching a livestream on YouTube. Suddenly Safari crashed and I got a fairly long error message window which got sent to Apple.


This has never happened before, and I started the process of reinstalling the system. If this is the case, should I worry about my iPhone or iCloud account as well?


The message: “object cannot be nil.”

Is this something that can happen by random?


This is part of the message:


Crashed Thread:    14 Dispatch queue: com.apple.SafariShared.WBSHistoryServiceStore


Exception Type:    EXC_CRASH (SIGABRT)

Exception Codes:   0x0000000000000000, 0x0000000000000000

Exception Note:    EXC_CORPSE_NOTIFY


Application Specific Information:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSSetM addObject:]: object cannot be nil'

terminating with uncaught exception of type NSException

abort() called


The rest is divided into, with several lines on each thread:


Application Specific Backtrace 1:


Thread 0:: Dispatch queue: com.apple.main-thread


Thread 1:: JavaScriptCore bmalloc scavenger


Thread 2:: com.apple.coreanimation.render-server


Thread 3:: com.apple.NSEventThread


Thread 4:: com.apple.CFSocket.private


Thread 5:: AMCP Logging Spool


Thread 6:: com.apple.CFNetwork.CustomProtocols


Thread 7:: com.apple.NSURLConnectionLoader


Thread 8-11:: (no text)


Thread 12:: CVDisplayLink


Thread 13:: (no text)


Thread 14 Crashed:: Dispatch queue: 


Thread 15-20:: (no text)


Thread 14 crashed with X86 Thread State (64-bit):


Thread 14 instruction stream not available.


Thread 14 last branch register state not available.


Binary images: (extremely long!)


External Modification Summary:

 Calls made by other processes targeting this process:

  task_for_pid: 75

  thread_create: 0

  thread_set_state: 0

 Calls made by this process:

  task_for_pid: 0

  thread_create: 0

  thread_set_state: 0

 Calls made by all processes on this machine:

  task_for_pid: 35522

  thread_create: 0

  thread_set_state: 0


VM Region Summary:

ReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)

Writable regions: Total=1.8G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.8G(100%)


MacBook Air 13″, macOS 11.2

Posted on Feb 19, 2021 1:58 PM

Reply

Similar questions

5 replies

Feb 19, 2021 2:22 PM in response to olav.e

Not Hacked and guess one when into Console and fished out the Error to post in these Forums. First off, sometimes but rare, Safari may encounter something it does not like and crash. It may have something with a Safari Extension that malfunctioned and took Safari down / crash.


Reinstallation is drastic move but if you are confident this will solve the issue - so be it. Just suggest having a recent Time Machine Backup

Feb 19, 2021 2:34 PM in response to olav.e

No, not hacked. It's a bug in something you have running. The error spells out what's wrong, which you noted:


*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSSetM addObject:]: object cannot be nil'

terminating with uncaught exception of type NSException


A call in whichever app is the culprit tried to apply a value of nil to an object that cannot be nil. That's a guaranteed crash.

Feb 19, 2021 2:43 PM in response to olav.e

olav.e wrote:
but now I am stuck in a -1008F error, so looks like I am kind of stuck and will be without laptop for a while.

that error is very specific.

If your Mac starts up to error -1008F - Apple Support

read the article then try using a wired ethernet connection and try again. when using wi-fi, the download can sometimes be corrupted or may not complete at all.

Feb 19, 2021 2:30 PM in response to Owl-53

That’s good news :) But wish the error code would tell more about level of concern.


I don’t have any extensions and almost all apps installed from App Store.


I wanted a fresh install. And I don’t mind a fresh install once a year. So I used the disk utility solution when restarting with cmd+r, but now I am stuck in a -1008F error, so looks like I am kind of stuck and will be without laptop for a while.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Am I hacked? EXC_CRASH (SIGABRT)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.