re: Core Data and retain count

FROM : Ben Trumbull
DATE : Mon Mar 03 02:35:50 2008

> My question is, why would changing a property value cause another
> property to have its retain count increase?


No idea.  Why don't you run it in gdb and break on the -retain method 
and get some stack traces ?
This works best if the class you're debugging (in this case the value 
window controller) has a custom retain/release method that you can 
break on instead of NSObject's etc.  If it doesn't, you can trivially 
make one by adding a category on it and putting -retain/-release/-
autorelease methods on it that simply call super.

> So by the time the user wants to delete a managed object from the 
> list, the window controller could have a high
> value and is never released!


This sounds like a hypothetical concern as opposed to an empirically 
observed leak.  Each retainer is obliged to balance itself out 
eventually.  That's not your problem.  Generally speaking, the retain 
count is an implementation dependent value and not really meaningful 
API.

- Ben