• 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: Cocoa-dev Digest, Vol 5, Issue 393
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa-dev Digest, Vol 5, Issue 393


  • Subject: Re: Cocoa-dev Digest, Vol 5, Issue 393
  • From: Nick Zitzmann <email@hidden>
  • Date: Wed, 12 Mar 2008 11:47:38 -0600


On Mar 12, 2008, at 11:35 AM, Daniel Child wrote:

Each record is allocated and explicitly released at the end of the loop after adding it to the table. I thought autorelease might wait too long to get rid of it, so I do it explicitly.

As for Instruments, unfortunately I'm doing this on Tiger.


If you're using Tiger, then you'd use ObjectAlloc to keep track of objects created by your app, and MallocDebug to look for leaks. And I hope you have plenty of RAM on hand, since ObjectAlloc will devour it all...

Anyway, you want to look for hills and plateaus in object creation, e.g. lots of objects that get created at once, and then released all at once.

Nick Zitzmann
<http://www.chronosnet.com/>

_______________________________________________

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


  • Follow-Ups:
    • Re: runtime error (-> ObjectAlloc)
      • From: Daniel Child <email@hidden>
References: 
 >Re: Cocoa-dev Digest, Vol 5, Issue 393 (From: Daniel Child <email@hidden>)

  • Prev by Date: Re: Cocoa-dev Digest, Vol 5, Issue 393
  • Next by Date: Re: memory warnings
  • Previous by thread: Re: runtime error
  • Next by thread: Re: runtime error (-> ObjectAlloc)
  • Index(es):
    • Date
    • Thread