EXC_CRASH (SIGABRT) CFRunLoopRunSpecific

Question

MarcoCarnevali OP

Created Jan ’23

Replies 2

Boosts 0

Views 1.2k

Participants 3

Hello, I'm seeking some help after looking at some of our crash log reports. I'll post here one example:

crashlog.crash

From the look of it, seems to be a crash caused by the OS. Reason being that looking at the thread 0, the frame 10 is our app setting up the AppDelegate (AppDelegate.swift:11 is the class declaration). After that all the other frames are specifying code deep in the UIKit and CoreFoundation frameworks. Have anyone seen something like that? Could this be an out-of-memory crash? Thanks in advance!

Boost

Answer 1

avetis OP

Jan ’23

I am also experiencing the same problem.

crashlog-58F24E2C-F710-4CAA-BF66-008DF235A9A1 1.crash

0

Answer 2

DTS Engineer OP

Apple

Jan ’23

This crash report is weird. Consider this:

Exception Type:  EXC_CRASH (SIGABRT)

This usually means that the app crashed itself by calling abort. However, the crashing thread backtrace:

Thread 0 Crashed:
0   libsystem_kernel.dylib … mach_msg2_trap + 8 …
1   libsystem_kernel.dylib … mach_msg2_internal + 80 …
2   libsystem_kernel.dylib … mach_msg_overwrite + 388 …
3   libsystem_kernel.dylib … mach_msg + 24 …
4   CoreFoundation         … __CFRunLoopServiceMachPort + 160 …
5   CoreFoundation         … __CFRunLoopRun + 1232 …
6   CoreFoundation         … CFRunLoopRunSpecific + 612 …
7   GraphicsServices       … GSEventRunModal + 164 …
8   UIKitCore              … -[UIApplication _run] + 888 …
9   UIKitCore              … UIApplicationMain + 340 …
10  Driver                 … main + 68 …
11  dyld                   … start + 2528 …

shows no sign of anything that could trigger a SIGABRT. That leaves two theories:

Someone is sending the SIGABRT signal from outside your process.
Something is messing up your crash report.

With regards the first, I’ve never seen that happen on iOS. Which suggests the second. And this is worrisome:

Thread 4 name:
Thread 4:
0   libsystem_kernel.dylib  … mach_msg2_trap + 8 …
1   libsystem_kernel.dylib  … mach_msg2_internal + 80 …
2   libsystem_kernel.dylib  … mach_msg_overwrite + 388 …
3   libsystem_kernel.dylib  … mach_msg + 24 …
4   Driver                  … handleExceptions + 172 …
5   libsystem_pthread.dylib … _pthread_start + 148 …
6   libsystem_pthread.dylib … thread_start + 8 …

Frame 4 look like a third-party crash reporter. Such things are fundamentally unreliable. For an explanation as to why, see Implementing Your Own Crash Reporter.

My advice is that you remove your third-party crash reporter. If you continue to see crashes, please reply on this thread, including an Apple crash report per the instructions in Posting a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1