I'm collecting and uploading MetricKit crash diagnostic reports from my app in the field, and the huge majority of the reports I get back have exception type EXC_CRASH, signal SIGKILL with no terminationReason. The report lists thread 0 as attributed, but it doesn't have any of my code active. Here's an example symbolicated trace of thread 0:
mach_msg2_trap (in libsystem_kernel.dylib) + 8
mach_msg2_internal (in libsystem_kernel.dylib) + 76
mach_msg_overwrite (in libsystem_kernel.dylib) + 424
mach_msg (in libsystem_kernel.dylib) + 24
__CFRunLoopServiceMachPort (in CoreFoundation) + 160
__CFRunLoopRun (in CoreFoundation) + 1188
_CFRunLoopRunSpecificWithOptions (in CoreFoundation) + 532
GSEventRunModal (in GraphicsServices) + 120
-[UIApplication _run] (in UIKitCore) + 796
UIApplicationMain (in UIKitCore) + 332
main (in BRFree) (main.m:0)
start (in dyld) + 6928
There is code from my app in other threads, but they're all waiting on NSConditions and not doing anything.
I thought they might be 0xdead10cc crashes, but there are other reports that have "terminationReason": "Namespace RUNNINGBOARD, Code 0xdead10cc".
Can anyone help me narrow down what could be causing these crashes?
I would file a DTS support ticket, but it won't let me without either a request from someone at Apple or a focused test project. If an engineer sees this thread and gives me a green light for a code-level support request, I can provide a sampling of the MetricKit reports.
