• 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
Re: alloc init thread safe?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: alloc init thread safe?


  • Subject: Re: alloc init thread safe?
  • From: David Carlisle <email@hidden>
  • Date: Fri, 9 Mar 2007 09:11:48 -0700

So is there a style of usage of [Class alloc] that will detect the craziness when memory runs out and it returns nil? I'm just realizing that putting "if ( self=[super init] )" into my init methods won't solve that problem.

On Mar 9, 2007, at 7:58 AM, James Bucanek wrote:

NSZombies basically keeps every object you ever allocated around forever. I have some very object-intensive routines that spew millions of temporary objects. Some of these can't be debugged with NSZombie because the application will run out of memory space before it gets to the bug. When it does [Class alloc] returns nil, and much craziness ensues.

_______________________________________________

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


  • Follow-Ups:
    • Re: alloc init thread safe?
      • From: Rosyna <email@hidden>
References: 
 >Re: alloc init thread safe? (From: James Bucanek <email@hidden>)

  • Prev by Date: Re: alloc init thread safe?
  • Next by Date: Re: alloc init thread safe?
  • Previous by thread: Re: alloc init thread safe?
  • Next by thread: Re: alloc init thread safe?
  • Index(es):
    • Date
    • Thread