On May 24, 2012, at 10:26 AM, Jonathan Taylor <j.m.tay...@durham.ac.uk> wrote:
> I have been battling a retain cycle for a couple of hours, assuming I am at > fault, but I am starting to think there is something fishy going on. Can > anybody advise? > > - I have a window controller subclass (and associated window) A, and a > separate window controller subclass (and associated window) B. B contains a > property, designated 'retain', that keeps a pointer to A. B is > programatically closed first, and later on A is programatically closed > - I believe that I am correctly balancing retain/release for A. > - I believe I am doing the same for B. Please post your code. > > 1. If I do not set B's pointer to A, both A and B are deallocated correctly > 2. If instead I set B's pointer to A, but reset it to nil just before B is > closed, both A and B are deallocated correctly > 3. If instead B still has a live pointer to A when B is closed, this should > be autoreleased by the runtime, which it is. However, A never gets > deallocated. If A somehow has a chain of retains that keeps B alive, #3 is wrong. Your approach with #2 seems sensible. > > There appears to be some weird runtime voodoo behind the scenes involving > NSAutounbinder, which I think is what should ultimately be sending the final > release to A. That is what sends the final release to B, but that final > release for A is missing under that third scenario above. It sounds like you're (erroneously) associating an autorelease coming from some framework code with a retain that you're performing yourself. > --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
