arc下dealloc的处理.docxVIP

ARC下dealloc过程的探究我是前言这次探索源自于自己一直以来对ARC的一个疑问，在MRC时代，经常写下面的代码：123456789- (void)dealloc{self.array = nil;self.string = nil; // ... // // 非Objc对象内存的释放，如CFRelease(...) // ... // [super dealloc];}对象析构时将内部其他对象release掉，申请的非Objc对象的内存当然也一并处理掉，最后调用super，继续将父类对象做析构。而现如今到了ARC时代，只剩下了下面的代码：123456- (void)dealloc{ // ... // // 非Objc对象内存的释放，如CFRelease(...) // ... //}问题来了：这个对象实例变量（Ivars）的释放去哪儿了？没有显示的调用[super dealloc]，上层的析构去哪儿了？ARC文档中对dealloc过程的解释llvm官方的ARC文档中对ARC下的dealloc过程做了简单说明，从中还是能找出些有用的信息：A class may provide a method definition for an instance method named dealloc. This method will be called after the final release of the object but before it is deallocated or any of its instance variables are destroyed. The superclass’s implementation of dealloc will be called automatically when the method returns.大概意思是：dealloc方法在最后一次release后被调用，但此时实例变量（Ivars）并未释放，父类的dealloc的方法将在子类dealloc方法返回后自动调用The instance variables for an ARC-compiled class will be destroyed at some point after control enters the dealloc method for the root class of the class. The ordering of the destruction of instance variables is unspecified, both within a single class and between subclasses and superclasses.理解：ARC下对象的实例变量在根类[NSObjectdealloc]中释放（通常root class都是NSObject），变量释放顺序各种不确定（一个类内的不确定，子类和父类间也不确定，也就是说不用care释放顺序）所以，不用主调[super dealloc]是因为自动调了，后面再说如何实现的；ARC下实例变量在根类NSObject析构时析构，下面就探究下。NSObject的析构过程通过apple的runtime源码，不难发现NSObject执行dealloc时调用_objc_rootDealloc继而调用object_dispose随后调用objc_destructInstance方法，前几步都是条件判断和简单的跳转，最后的这个函数如下：12345678910111213141516171819void *objc_destructInstance(idobj) {if (obj) { Class isa_gen = _object_getClass(obj);class_t *isa = newcls(isa_gen);// Read all of the flags at once for performance.boolcxx = hasCxxStructors(isa);bool assoc = !UseGC _class_instancesHaveAssociatedObjects(isa_gen);// This order is important.if (cxx) object_cxxDestruct(obj);if (assoc) _object_remove_assocations(obj);if (!UseGC) objc_clear_deallocating(obj); }returnobj;}简单明确的干了三件事：执行一个叫object_c