• 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 19:51:04 -0700
  • Thread-topic: if statement causing 32 Byte leak?

> Just a quick note: one problem with this is false positives; you don't
> necessarily control all the code that handles the object in question.

I think perhaps you didn't notice that he said "at -dealloc time". There is
no case in which an autorelease pool should have a reference to an object
when the object is being dealloc'd. At all other times of course, there may
be references in autorelease pools which were correctly put there by library
code after a retain.

--
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

  • Follow-Ups:
    • Re: if statement causing 32 Byte leak?
      • From: Dave Camp <email@hidden>
References: 
 >Re: if statement causing 32 Byte leak? (From: Chris Parker <email@hidden>)

  • Prev by Date: Re: if statement causing 32 Byte leak?
  • Next by Date: How to know whether property in Cocoa class is KVO-compliant?
  • Previous by thread: Re: if statement causing 32 Byte leak?
  • Next by thread: Re: if statement causing 32 Byte leak?
  • Index(es):
    • Date
    • Thread