0 CFNetwork 0x2e999860 invocation function for block in URLConnectionClient_Classic::invalidateAsync(dispatch_queue_s*, void () block_pointer) 1 CFNetwork 0x2e9cb336 invocation function for block in CoreSchedulingSet::_performAsync(char const*, void () block_pointer) const 2 CFNetwork 0x2e9cb336 invocation function for block in CoreSchedulingSet::_performAsync(char const*, void () block_pointer) const 3 CoreFoundation 0x2ec63ea0 _CFArrayApplyFunction 4 CFNetwork 0x2e931e04 RunloopBlockContext::perform() 5 CFNetwork 0x2e931cd4 MultiplexerSource::perform() 6 CFNetwork 0x2e931b64 MultiplexerSource::_perform(void*) 7 CoreFoundation 0x2ecfbf1e ___CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 8 CoreFoundation 0x2ecfb3e6 ___CFRunLoopDoSources0 9 CoreFoundation 0x2ecf9bd6 ___CFRunLoopRun 10 CoreFoundation 0x2ec64470 _CFRunLoopRunSpecific 11 CoreFoundation 0x2ec64252 _CFRunLoopRunInMode 12 GraphicsServices 0x3399e2ea 0x33997000 + 29418 13 UIKit 0x31519844 _UIApplicationMain 14 QQ 0x002c205c _main(main.m:22) 15 QQ 0x0020defc start SEGV_ACCERR
1、怀疑点: dipatch_async回调回来,self早就被析构,证明不是
GCD中一个现象:在一个类中使用dispatch_async执行异步任务,任务未完成之前释放对象,并不能调用对象的dealloc,而是在任务完成后才去调用dealloc.
很常见的一个例子就是异步下载图片,图片未下载完成之前页面返回,并不会立马调用dealloc,而是在下载完成后才去调用dealloc.
经测试发现,当开始任务的时候GCD对对象添加了引用,导致对象的引用计数+1,所以释放对象时并不能真正释放,必须等任务完成后才能真正释放对象,而GCD中也无cancel,这种现象也没引起内存泄露,很奇怪。
2、