• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSWindowController subclasses, and retain cycles
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSWindowController subclasses, and retain cycles


  • Subject: Re: NSWindowController subclasses, and retain cycles
  • From: Charles Srstka <email@hidden>
  • Date: Thu, 24 May 2012 10:25:03 -0500

On May 24, 2012, at 10:21 AM, Fritz Anderson wrote:

> On 24 May 2012, at 9:26 AM, Jonathan Taylor wrote:
>
>> - 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.
>>
>> 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.
>
> Why do you believe that a retain @property does not always require a release (set to nil)? The autorelease you seem to have detected was sent by a completely different chain of execution to balance a retain made in that chain. The operating system does not magically know that you're done with B's retention of A; you have to balance your own retains with your own releases. (2) works because it is correct.

It’s ambiguous from the original post, but since he only points out that A never gets deallocated, my assumption is that B *does* get deallocated. If this is the case, A should get released in B’s dealloc method (unless he’s not using ARC and forgot to do this).

Charles
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


References: 
 >NSWindowController subclasses, and retain cycles (From: Jonathan Taylor <email@hidden>)
 >Re: NSWindowController subclasses, and retain cycles (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: NSWindowController subclasses, and retain cycles
  • Next by Date: Re: stringWithFormat / Rendering Text (iOS)
  • Previous by thread: Re: NSWindowController subclasses, and retain cycles
  • Next by thread: Re: NSWindowController subclasses, and retain cycles
  • Index(es):
    • Date
    • Thread