How Retain cycles occurs in Memory Management?

Question

Can some explain the retain cycles problem with a sample program?

Answer 1

I've got just the right article(s) for you:

http://cocoawithlove.com/2010/06/assign-retain-copy-pitfalls-in-obj-c.html

http://cocoawithlove.com/2009/07/rules-to-avoid-retain-cycles.html

http://developer.apple.com/iphone/library/documentation/Cocoa/Conceptual/MemoryMgmt/MemoryMgmt.html

http://www.markj.net/iphone-memory-management-tutorial-video/

Answer 2

Consider the following:

NSMutableArray *a = [NSMutableArray array];
NSMutableArray *b = [NSMutableArray array];
[a addObject:b];
[b addObject:a];

When b is inserted into a, b is retained, likewise a when its inserted into b. As both now have a strong reference to each other, neither will get deallocated unless you manually break the cycle by e.g. removing one from the other.

Note that the Cocoa Memory Management guide also contains a section on retain cycles and includes an explanation of weak references, which help with these problems.