Re: NSWindow and autorelease with dynamic binary
Re: NSWindow and autorelease with dynamic binary
- Subject: Re: NSWindow and autorelease with dynamic binary
- From: John Stiles <email@hidden>
- Date: Tue, 15 Jan 2008 09:23:47 -0800
Perhaps your window is already set to release-on-close, so the extra
release is actually a problem?
On Jan 15, 2008, at 2:18 AM, Wesley Smith wrote:
Hi,
I've managed to track my crashing problems with a Cocoa dynamically
loaded binary down to some NSAutoreleasePool stuff. If I close the
NSWindow by clicking on the red button in the topleft, and _then_
quite the app, no crashing. If I quite the app with an active window,
I do get crashing after the dynamic binary has been unloaded and the
app is in its final stack unwind. What happens is:
objc_msgSend <-------------------------------------- CRASH
EXC_BAD_ACCESSS
NSPopAutoReleasePool
+[NSAutoreleasePoop releaseAllPools]
which makes sense if a reference is left over. My question is how can
I guarantee that all such things have been taken care of? In my
dynamic binary teardown, I call
[window close];
[window release];
I thought this would be enough but apparently not.
Any ideas?
thanks,
wes
_______________________________________________
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:
40blizzard.com
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