• 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
GC Re: Questions about Nib Object Retention
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GC Re: Questions about Nib Object Retention


  • Subject: GC Re: Questions about Nib Object Retention
  • From: Fritz Anderson <email@hidden>
  • Date: Wed, 21 Oct 2009 09:45:26 -0500

All this leads me to the paragraph about top-level objects under garbage collection:

===
Mac OS X - garbage collected memory model
Most objects in the graph are kept in memory through strong references between the objects. Only the top-level objects in the nib file do not have strong references initially. Thus, your code must create strong references to these objects to prevent the object graph from being released.
===


Does this mean that there's a race between the NIB loader's need to create a strong reference and the GC thread's imperative to collect the object before it is referenced?

	— F

_______________________________________________

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: GC Re: Questions about Nib Object Retention
      • From: "Clark S. Cox III" <email@hidden>
    • Re: GC Re: Questions about Nib Object Retention
      • From: Bill Bumgarner <email@hidden>
References: 
 >Questions about Nib Object Retention (From: an0 <email@hidden>)

  • Prev by Date: Re: Hiding tab view items
  • Next by Date: Re: info gc-roots interpretation
  • Previous by thread: Re: Questions about Nib Object Retention
  • Next by thread: Re: GC Re: Questions about Nib Object Retention
  • Index(es):
    • Date
    • Thread