Re: NSAutoreleasePool causes crashes when empty?
Re: NSAutoreleasePool causes crashes when empty?
- Subject: Re: NSAutoreleasePool causes crashes when empty?
- From: John Stiles <email@hidden>
- Date: Thu, 03 Apr 2008 17:41:18 -0700
I'd suspect some sort of error in your app, e.g. perhaps "pool" itself
has never been alloc/inited and contains garbage. [pool release] on a
valid but empty NSAutoreleasePool is perfectly harmless.
Kevin Dixon wrote:
I have a method in my class that's a thread entry point, using
detachNewThreadSelector. According to the docs, I create an
NSAutoreleasePool and release it at the end of the thread's life (right
before [NSThread exit].
The thread calls a single routine from another class. Sometimes this
routine aborts before allocating any objects that would be autoreleased
(due to an error situation). I notice when this is the case, calling [pool
release] causes a crash, but if the objects are allocated normally due to
the full run of the function, then no crash occurs.
Is there a way I can query the pool to see if it needs to be released, or
should I implement some sort of return code from my other function to see
if I should release the pool or not.
Thanks,
-Kevin
_______________________________________________
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
_______________________________________________
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