Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
- Subject: Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
- From: Rosyna <email@hidden>
- Date: Mon, 18 Dec 2006 18:52:06 -0700
Well, deallocating an outer pool deallocates all inner pools.
http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Concepts/AutoreleasePools.html#//apple_ref/doc/uid/20000047-997594
Mentions this specifically.
But yeah, you should release any autorelease pools in the same
context in which they were created due to this "stacking" behaviour.
Ack, at 12/18/06, John Stiles said:
Unless your app is doing very clever things, there isn't any
justification for allocating an autorelease pool without releasing
it.
These are particularly tricky because they are implemented in a
stack, and if you do not keep the stack properly balanced, it is
quite easy to make crash-inducing mistakes.
--
Sincerely,
Rosyna Keller
Technical Support/Carbon troll/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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