本文介绍了无法理解MyApp崩溃的位置的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我的应用程序在某些情况下崩溃。无法找到原因&崩溃的地方。
My App is crashing in some scenarios. Unable to find the reason & place of crash.
下面是崩溃日志(iPad / iOS 8.0.2)。
Below is crash log (iPad/iOS 8.0.2).
Hardware Model: iPad2,5
OS Version: iOS 8.0.2 (12A405)
Report Version: 105
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x306b3dfc __pthread_kill + 8
1 libsystem_pthread.dylib 0x30733d0e pthread_kill + 58
2 libsystem_c.dylib 0x30653934 abort + 72
3 libc++abi.dylib 0x2f864bb8 abort_message + 84
4 libc++abi.dylib 0x2f87e66a default_terminate_handler() + 262
5 libobjc.A.dylib 0x30052f0e _objc_terminate() + 190
6 libc++abi.dylib 0x2f87bdec std::__terminate(void (*)()) + 76
7 libc++abi.dylib 0x2f87b5ac __cxa_throw + 108
8 libobjc.A.dylib 0x30052d46 objc_exception_throw + 246
9 CoreFoundation 0x225dfe58 +[NSException raise:format:arguments:] + 100
10 Foundation 0x232af2c4 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 88
11 BaseBoard 0x270a08d8 __25-[BSAction sendResponse:]_block_invoke + 140
12 libdispatch.dylib 0x305bc99c _dispatch_barrier_sync_f_invoke + 44
13 BaseBoard 0x270a0842 -[BSAction sendResponse:] + 98
14 UIKit 0x25fd54d0 -[UIFetchContentInBackgroundAction sendResponse:] + 212
15 libdispatch.dylib 0x305b3610 _dispatch_call_block_and_release + 8
16 libdispatch.dylib 0x305b35fc _dispatch_client_callout + 20
17 libdispatch.dylib 0x305be2b2 _dispatch_main_queue_callback_4CF$VARIANT$mp + 714
18 CoreFoundation 0x225a5e5c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 4
19 CoreFoundation 0x225a457c __CFRunLoopRun + 1508
20 CoreFoundation 0x224f1dac CFRunLoopRunSpecific + 472
21 CoreFoundation 0x224f1bbe CFRunLoopRunInMode + 102
22 GraphicsServices 0x2985404c GSEventRunModal + 132
23 UIKit 0x25abda2c UIApplicationMain + 1436
24 MyApp 0x000fb9f2 main (main.m:15)
25 libdyld.dylib 0x305eeaac start + 0
提前致谢..
推荐答案
与堆栈跟踪对应的异常消息是:
The exception message that corresponds to the stack trace is:
虽然不可能单独从堆栈中确定,但您最有可能被称为completionHandler传递给你的app delegate的-application:performFetchWithCompletionHandler:方法两次。
While it's not possible to tell for sure from the stack alone, you most likely called the completionHandler passed to your app delegate's -application:performFetchWithCompletionHandler: method twice.
这篇关于无法理解MyApp崩溃的位置的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!