Re: NSAutoreleasePool dilemma
Re: NSAutoreleasePool dilemma
- Subject: Re: NSAutoreleasePool dilemma
- From: John Stiles <email@hidden>
- Date: Wed, 19 Oct 2005 15:21:57 -0700
On Oct 19, 2005, at 3:04 PM, David Catmull wrote:
On Oct 19, 2005, at 2:55 PM, John Stiles wrote:
You need an autorelease pool around any [foo release], unfortunately.
Does this apply even to autorelease pools? The message happens when
I release the pool itself. If you have to have a pool to release a
pool, what do you do with the last one?
If it's happening right when you release the autorelease pool, then I
don't know what you could do to solve it :) That just sounds like an
OS bug.
I was running under the theory that it's happening sometime after the
autorelease pool goes away, but if it's definitely happening on the
line where you release the autorelease pool, I don't know. Maybe go
into gdb and set breakpoints on NSLog/fprintf/etc; then you could see
the exact stack crawl for the allocation.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden