I will check the codes of third-party crash reporter.
Cool.
For the sake of other folks reading this thread, I want to clarify this comment:
It looks [your] third-party crash reporter [has] disrupted the crash state seen by the Apple crash reporter.
What brought me to that conclusion? Well, consider this snippet from your crash report:
Exception Type: EXC_CRASH (SIGSEGV)
…
Triggered by Thread: 0
This indicates that your app crashed because of a memory access exception on thread 0. However, the backtrace for thread 0 is this:
Thread 0 name:
Thread 0 Crashed:
0 libsystem_kernel.dylib … mach_msg_trap + 8
1 libsystem_kernel.dylib … mach_msg + 72 (mach_msg.c:103)
2 CoreFoundation … __CFRunLoopServiceMachPort + 216 (CFRunLoop.c:2575)
3 CoreFoundation … __CFRunLoopRun + 1444 (CFRunLoop.c:2931)
4 CoreFoundation … CFRunLoopRunSpecific + 464 (CFRunLoop.c:3192)
5 GraphicsServices … GSEventRunModal + 104 (GSEvent.c:2246)
6 UIKitCore … UIApplicationMain + 1936 (UIApplication.m:4773)
7 MYAPP … main + 152 (main.m:16)
8 libdyld.dylib … start + 4
This means that thread 0 was blocked inside UIKit’s main thread run loop waiting for an event. How can it trigger a memory access exception while blocked? That’s possible, but very unlikely.
Looking through the rest of your crash report I see this:
Thread 21 name:
Thread 21:
0 libobjc.A.dylib … objc_release + 16 (objc-object.h:551)
1 CFNetwork … URLResponse::~URLResponse() + 52 (AutoTypes.h:39)
2 libobjc.A.dylib … object_cxxDestructFromClass(objc_object*, objc_class*) + 112 (objc-class.mm:452)
3 libobjc.A.dylib … objc_destructInstance + 88 (objc-class.mm:467)
4 libobjc.A.dylib … _objc_rootDealloc + 48 (objc-runtime-new.mm:7606)
5 CFNetwork … -[NSURLResponseInternal dealloc] + 40 (NSURLResponse.mm:63)
6 CFNetwork … -[NSURLResponse(NSURLResponsePrivate) dealloc] + 28 (NSURLResponse.mm:351)
7 CFNetwork … -[NSHTTPURLResponse dealloc] + 64 (NSURLResponse.mm:622)
…
That’s a much more likely cause for this crash. However, we can’t be sure because something has caused the crash reporter to point to the wrong thread. The presence of a third-party crash reporter in the backtrace of thread 1 is by far the most likely explanation of that disruption.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"