• 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: CFMessagePort and GC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CFMessagePort and GC


  • Subject: Re: CFMessagePort and GC
  • From: "Michael Ash" <email@hidden>
  • Date: Mon, 1 Dec 2008 12:02:46 -0500

On Mon, Dec 1, 2008 at 12:19 AM, Ryan Brown <email@hidden> wrote:
> Also, forgot to mention: calling either objc_collect_if_needed() or
> [[NSGarbageCollector defaultCollector] collectExhaustively] after releasing
> the run loop source and message port doesn't force an immediate
> deallocation. Not sure why.

Most likely because the object is still referenced on the stack, and
so is still considered live. If you're sure that you've eliminated all
stack references to it (returned from any functions that may have used
it), then you can clear the stack using the objc_clear_stack()
function. Check the docs or list archives for more information on
that.

Mike
_______________________________________________

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

  • Prev by Date: RE: [ANN]CocoaOniguruma Released
  • Next by Date: Power code unplug and plug
  • Previous by thread: RE: [ANN]CocoaOniguruma Released
  • Next by thread: Power code unplug and plug
  • Index(es):
    • Date
    • Thread