FROM : Shawn Erickson
DATE : Mon Jul 31 20:55:57 2006
On 7/31/06, Drarok Ithaqua <<email_removed>> wrote:
> It's It's definitely not my own now. I've got my app to run
> perfectly, but as soon as I add the 3rd party NSProgressIndicator in,
> I get a ton of retain/releases, and my window doesn't dealloc.
> A retain cycle sounds like the right term, it seems like an almost
> infinite loop, but if I set the focus to another app, then back to mine,
> the window is dealloced and the massive loop of retain/releases stops.
A retain cycle is simply two objects retaining each other either
directly or by a set of intermediate objects such that they will never
be deallocated since the always maintain a retain on each other. They
come about if you don't consider parent / child object ownership type
concepts.
I wasn't using that term to say anything about the numerous
retain/release messages you are seeing (again those may not be a
problem at all... just a cost of the implementation you have).
-Shawn
DATE : Mon Jul 31 20:55:57 2006
On 7/31/06, Drarok Ithaqua <<email_removed>> wrote:
> It's It's definitely not my own now. I've got my app to run
> perfectly, but as soon as I add the 3rd party NSProgressIndicator in,
> I get a ton of retain/releases, and my window doesn't dealloc.
> A retain cycle sounds like the right term, it seems like an almost
> infinite loop, but if I set the focus to another app, then back to mine,
> the window is dealloced and the massive loop of retain/releases stops.
A retain cycle is simply two objects retaining each other either
directly or by a set of intermediate objects such that they will never
be deallocated since the always maintain a retain on each other. They
come about if you don't consider parent / child object ownership type
concepts.
I wasn't using that term to say anything about the numerous
retain/release messages you are seeing (again those may not be a
problem at all... just a cost of the implementation you have).
-Shawn






Cocoa mail archive

