• 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: Memory Management and DO
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory Management and DO


  • Subject: Re: Memory Management and DO
  • From: Chris Kane <email@hidden>
  • Date: Wed, 20 Jun 2001 14:36:13 -0500

On Sunday, June 17, 2001, at 05:37 PM, Thierry Faucounau wrote:
I've been using ObjectAlloc to track memory leaks in my app and have empirically determined the following behavior which I would like to confirm is correct.

There is an extra retain in NSInvocation in 10.0 on the return value, for methods which return objects. This was fixed for the next release (no pun intended). Since DO uses NSInvocation, this shows up in DO as well.

If you workaround this, be sure to note what you've done so you can eliminate the workaround later (which may cause premature freeing).


Chris Kane
Cocoa Frameworks, Apple Computer


  • Follow-Ups:
    • Re: Memory Management and DO
      • From: Thierry Faucounau <email@hidden>
References: 
 >Memory Management and DO (From: Thierry Faucounau <email@hidden>)

  • Prev by Date: Re: retain, release, autorelease (was Checkboxes and NSBox titles)
  • Next by Date: Re: CoreFoundation <==> Foundation?
  • Previous by thread: Memory Management and DO
  • Next by thread: Re: Memory Management and DO
  • Index(es):
    • Date
    • Thread