• 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
NSInvocation leak
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSInvocation leak


  • Subject: NSInvocation leak
  • From: Chris Kane <email@hidden>
  • Date: Thu, 2 Aug 2001 10:43:22 -0700

This leak is known, and has been mentioned here before (or was it on the OmniGroup list? -- hard to keep track). Here is the internal release note as it currently stands.

----
NSInvocation Excess Retain on Returned Value

As of <<internal release number omitted>>, a bug in Mac OS X 10.0(.x) where NSInvocation would retain the return value of an invoked method excess times, when the return value was an object, has been fixed. This most often manifests itself as an apparent leak of objects sent over Distributed Objects.

In 10.1, apps (and other executables) linked on 10.0(.x) will continue to over-retain the return value from NSInvocation, for compatibility. To get the fix, projects must be re-built on 10.1.
----

Chris Kane
Cocoa Frameworks, Apple


References: 
 >NSInvocation - MAJOR BUG? help!! (From: Steve Gehrman <email@hidden>)

  • Prev by Date: Re: Need Help with Help (Help Viewer now dies..)
  • Next by Date: Re: NSFileHandle notifications revisited
  • Previous by thread: NSInvocation - MAJOR BUG? help!!
  • Next by thread: RE: NSInvocation - MAJOR BUG? help!!
  • Index(es):
    • Date
    • Thread