I received the attached crash report. The problem is that the crash report does not contain the abort reason - it appears to be thrown in the GCD library with no additional information.
Is it a possible deadlock?
Any ideas?
Do you have a third-party crash reporter in play here?
The reason I ask is that your crash report is inconsistent. See this:
Crashed Thread: 15
and this:
Thread 0 Crashed:
and this:
Thread 15 Crashed:
The Apple crash reporter is generally pretty good about avoiding problems like this.
Anyway, assuming that thread 15 is the one that crashed, its backtrace looks like this:
Thread 15 Crashed:
0 libsystem_kernel.dylib … __pthread_kill + 10
1 libsystem_pthread.dylib … pthread_kill + 263 (pthread.c:1668)
2 libsystem_c.dylib … abort + 123 (abort.c:118)
3 libc++abi.dylib … abort_message + 241 (abort_message.cpp:78)
4 libc++abi.dylib … demangling_terminate_handler() + 266 (cxa_default_handlers.cpp:71)
5 libobjc.A.dylib … _objc_terminate() + 96 (objc-exception.mm:701)
6 libc++abi.dylib … std::__terminate(void (*)()) + 8 (cxa_handlers.cpp:59)
7 libc++abi.dylib … std::terminate() + 56 (cxa_handlers.cpp:88)
8 libdispatch.dylib … _dispatch_client_callout + 28 (object.m:563)
Frame 7 through 0 are what you see when some code throws an unhandled language exception. Frame 8 indicates that Dispatch is calling a block on queue. There’s no Last Exception Backtrace
section, so it’s likely that this was a C++ exception.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"