On Jan 4, 2010, at 11:50 AM, jonat...@mugginsoft.com wrote:
A recent post mentioned the concept of GC memory leakage.
How is is this defined? Is it merely a failure to nil out a rooted reference?
man heap(1) makes reference to over-rooted objects.
Are these merely objects with more than
jonat...@mugginsoft.com wrote:
A recent post mentioned the concept of GC memory leakage.
How is is this defined? Is it merely a failure to nil out a rooted reference?
Yes. If you hold a reference to memory you don't need anymore, you have
a leak.
I've gotten into huge flamewars over
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
On Mon, January 4, 2010 12:39:22 PM Bill Bumgarner b...@mac.com 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
On Jan 4, 2010, at 2:27 PM, Oftenwrong Soong wrote:
According to the docs, the collector scans all of your objects to determine
what needs to be deallocated. But in performing this scan, how does it know
which bits in your object are pointers to other objects and which bits are
just data?
On Jan 4, 2010, at 1:39 PM, jonat...@mugginsoft.com wrote:
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?
That is correct; the object may be referenced by multiple local
