Re: Can I somehow encourage the deallocation of a dismissed view controller?
Re: Can I somehow encourage the deallocation of a dismissed view controller?
- Subject: Re: Can I somehow encourage the deallocation of a dismissed view controller?
- From: G S <email@hidden>
- Date: Thu, 09 Feb 2012 00:17:56 -0800
Thanks again, Conrad.
> Are there *any* connections to your control (other than the
> superview/subview relationship)? I see a _NSSetObjectValueForKeyInIvar
> in your retain trace, which just be doing something internal, but it
> makes me wonder.
>
There is an IBOutlet for it, but that's it.
I discovered some problems in the XIB. There was a connection between a
nonexistent "delegate" member of the control to the file's owner, so I
deleted that. Why IB doesn't validate the connections after all these
years I don't know.
After I deleted the bogus connection, I noticed a profound change in the
order of retain/release calls. The pile of retains I documented was
immediately followed by an almost-completely balanced series of releases,
even before the view was displayed. Previously, the releases I documented
didn't occur until the view was dismissed.
However, the control still isn't deallocated when its parent view is.
That's where it stands currently. I haven't seen the crash since I cleaned
up the XIB connections, but that doesn't prove anything.
_______________________________________________
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