Does adding a KVO observer to self cause a memory leak?

Question

In a nsobject you have a property "keyPath" you want to observe itself and you use

[self addObserver:self forKeyPath:keyPath options:NSKeyValueObservingOptionNew context:nil];

Does the above line cause a retain cycle?

I present this question because I wanted to know if it was a viable alternative to rewriting a bunch of setter functions.

score 11 · Accepted Answer · answered Apr 06 '14 at 06:18

11

From the docs:

Neither the receiver, nor anObserver, are retained.

answered Apr 06 '14 at 06:18

zadr

Damn missed that part. "Discussion Neither the receiver, nor anObserver, are retained." – Yogurt Apr 06 '14 at 16:07
1

Learned my lesson. I made the mistake of only reading the popover text when clicking on the function call and holding option/alt, if I went to the action AppleDocs html I would have seen the discussion text that would have said that. Sorry for the trouble. – Yogurt Apr 07 '14 at 21:36
Because Apple doesn't take permalinks seriously, the info is still out there, but has moved here: https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/KeyValueObserving/Articles/KVOBasics.html#//apple_ref/doc/uid/20002252-BAJEAIEE Note: The key-value observing addObserver:forKeyPath:options:context: method does not maintain strong references to the observing object, the observed objects, or the context. You should ensure that you maintain strong references to the observing, and observed, objects, and the context as necessary. – nteissler Aug 31 '20 at 20:40

1 Answers1