• 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: Thierry Faucounau <email@hidden>
  • Date: Thu, 21 Jun 2001 13:17:27 -0600

Hi Chris,

Thanks for the info, this is what I feared. Do you have a vague ETA (I know you guys are not allowed to divulge dates) for the fix in NSInvocation? If you could say next 0.x software update, next major update, etc.. that would help a lot.

On Wednesday, June 20, 2001, at 01:36 PM, Chris Kane wrote:

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


--
Thierry Faucounau
Research Systems, Inc.


References: 
 >Re: Memory Management and DO (From: Chris Kane <email@hidden>)

  • Prev by Date: Re: WWDC Dev Tools / Software update
  • Next by Date: Re: NSArray init with a path
  • Previous by thread: Re: Memory Management and DO
  • Next by thread: Create NSArray from persistent storage
  • Index(es):
    • Date
    • Thread