A weak reference points to an object without keeping that object alive. It can break a retain cycle when two objects otherwise hold strong references to each other. section 7.3.3
Use weak references when closures, delegates, or notification listeners can accidentally retain their owning object. After the cycle is broken, memory can return to its earlier level after navigation. section 7.3.3
Breaking a navigation leak
Two objects strongly reference each other, so neither is released. Changing one reference to weak allows both to be released after navigation instead of leaving the screen in memory. section 7.3.3


