• 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: if statement causing 32 Byte leak?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: if statement causing 32 Byte leak?


  • Subject: Re: if statement causing 32 Byte leak?
  • From: Scott Ribe <email@hidden>
  • Date: Sun, 10 Jan 2010 13:27:28 -0700
  • Thread-topic: if statement causing 32 Byte leak?

> Actually, it would be nice to have *in a debugging context* since trying to
> track down a pointer that is in the autorelease pool the number of times it
> has been retained when you do a release would be very beneficial.  Yes, it
> would slow things down, but it would sure save a lot of time when trying to
> track down a spurious release!

I just override retain, release, autorelease and set breakpoints on them to
discover what's going on.

--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


_______________________________________________

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

References: 
 >Re: if statement causing 32 Byte leak? (From: "Glenn L. Austin" <email@hidden>)

  • Prev by Date: Re: How do I know when a new object is added to an NSArray or NSCollectionView?
  • Next by Date: Re: if statement causing 32 Byte leak?
  • Previous by thread: Re: if statement causing 32 Byte leak?
  • Next by thread: Re: if statement causing 32 Byte leak?
  • Index(es):
    • Date
    • Thread