• 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 retain count confusion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSWindowController retain count confusion


  • Subject: Re: NSWindowController retain count confusion
  • From: Jonathan Hess <email@hidden>
  • Date: Mon, 29 Sep 2008 20:20:00 -0700

Hey James -

The method -[NSObject retainCount] only exists to aid in debugging. You shouldn't be making any runtime decisions based on the return value of retainCount. You should only release something you previously retained/alloced/newed/copied or are for some other reason explicitly required to release. If you think you have a leak, you might consider running your app with Instruments's Object Alloc and Leaks tools. With those tools, you'll be able to get a backtrace for reach release, retain, and autorelease message sent to the instance of window you're curious about.

If you were to add a double release, and it wasn't the case that your class was responsible for a double retain, then as soon as the unbalanced retain is found and fixed, your program will start crashing.

Good luck -
Jon Hess

On Sep 29, 2008, at 7:30 PM, James Walker wrote:

I have an NSWindowController subclass that is defined as File's Owner in a nib. The window outlet is connected to a window, and the delegate outlet of the window goes back to the File's Owner. I was trying to release the controller in the windowWillClose: delegate method, but it didn't cause the dealloc method to be called. I found that immediately after creating the controller with alloc and init, its retain count was 1, but as soon as I did [self window], the retain count went up to 2. So, who's retaining the controller, and is it safe to just release it twice?

I searched the list, and found some old messages about NSWindowController retain counts being messed up by bindings, but I don't have any bindings (yet).
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________


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

_______________________________________________

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


  • Follow-Ups:
    • Re: NSWindowController retain count confusion
      • From: James Walker <email@hidden>
References: 
 >NSWindowController retain count confusion (From: James Walker <email@hidden>)

  • Prev by Date: NSWindowController retain count confusion
  • Next by Date: Drawing in a window with rounded corners
  • Previous by thread: NSWindowController retain count confusion
  • Next by thread: Re: NSWindowController retain count confusion
  • Index(es):
    • Date
    • Thread