• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSAutoreleasePool dilemma
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • Follow-Ups:
    • Re: NSAutoreleasePool dilemma
      • From: John Stiles <email@hidden>
  • Prev by Date: Re: Orange County cocoa heads interest?
  • Next by Date: [NSMutableDictionary setObject:forKey:] problem
  • Previous by thread: Re: views from nibs
  • Next by thread: Re: NSAutoreleasePool dilemma
  • Index(es):
    • Date
    • Thread