Re: GC memory leak - what is it?
Re: GC memory leak - what is it?
On 4 Jan 2010, at 20:39, Bill Bumgarner wrote:
>
> It isn't so much thinking of it as a reference that needs to be nil'd out as much as it is a need to properly disconnect a subgraph of objects from the live object graph in an application such that the subgraph is collected. That is, "nil'ing out references" is a fix for a symptom where the overarching problem is one of properly managing the connectivity of the object graph within the application.
>
> b.bum
Thanks for the clarification.
I am using the ObjectGraph tool in Instruments. The table view for this tool has a Root column.
Presumably a item marked as Root is one of : "global variables, stack variables, and objects with external references"
Browsing through User-defined Root objects I can see in the Extended Detail view that some of my objects have multiple stack roots.
How can a multiple stack root occur?
Is this just saying that the same object is referenced by multiple stack allocated pointers at the time that the sample was taken?
Presumably a stack root cannot be the source of any persistent leak as once the frame is gone so is the root.
Sorry if this is dumb question. I am struggling to comprehend just what the ObjectGraph tool is telling me.
Docs seem MIA for this tool (or maybe it's me that's MIA).
Most of my rooted objects are statically allocated singletons. ObjectGraph correctly identifies them as single roots.
Thanks again
Jonathan Mitchell
Developer
mugginsoft.com_______________________________________________
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