NSAutoreleasePool dilemma
NSAutoreleasePool dilemma
- Subject: NSAutoreleasePool dilemma
- From: David Catmull <email@hidden>
- Date: Wed, 19 Oct 2005 14:47:37 -0700
I'm doing some Cocoa stuff in a Carbon application. When I release my
autorelease pool, as the application is quitting, I get this message:
*** _NSAutoreleaseNoPool(): Object 0xb52c700 of class NSConcreteValue
autoreleased with no pool in place - just leaking
It seems like I have to have an autorelease pool in place in order to
release one, and the only way to win at that rate is to have a pool
that I never release. Is there a cleaner way around this?
--
David Catmull
email@hidden
http://www.uncommonplace.com/
_______________________________________________
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