Re: when should my NSWindowController be released?
Re: when should my NSWindowController be released?
- Subject: Re: when should my NSWindowController be released?
- From: Seth Willits <email@hidden>
- Date: Sat, 13 Sep 2008 01:32:47 -0700
On Sep 13, 2008, at 12:38 AM, Markus Spoettl wrote:
The process's entire memory space is freed when it terminates.
Because of this, objects may not ever receive a dealloc message.
The documentation for -[NSObject dealloc] discusses this.
Yes, I know but it isn't exactly helpful in determining whether
you're leaking memory or not. -dealloc: may not be called because
the system decides it's better not to - or - because you have a bug
in your memory management.
But application termination is obviously a special case. You don't
test for leaks by quitting your program. If dealloc is not called when
it should be (in a non-garbage-collected app), then you've probably
leaked it. (You may also just not realize that it really shouldn't
have been called yet ;-)
--
Seth Willits
_______________________________________________
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