Reference variable x GC

[Pekus Cons. e Desenvolvimento]

Hi,

I have seen some developers commenting that a reference variable is 'more
garbage collection eligible' if the programmer set its value to null after
using it, like this:

public void MemberFunction()
{
AnyClass refVar = new AnyClass ();

// Normal use of refVar functionalities

refVar = null;
}

Is it real? Any comment about?

Thanks,

Baccarin.

[Mickey Williams]

In this case, you won't get any benefit unless a collection occurs after the
variable is set to null and before the stack collapses after the method
returns to the caller. Since refVar is about to be evicted from the stack,
there's really no benefit to setting it to null. In other cases where the
time delta is greater, a live local reference to an object on the heap will
cause the object to be tracable, and therefore not eligible for collection.
However, in most cases this is a micro optimization, and won't buy you a
lot - especially if you're talking about local variables in methods that are
reasonably-sized.

Note also that setting a reference to null is not the same thing as
Dispose'ing it.
--
Mickey Williams
Author, "Microsoft Visual C# .NET Core Reference", MS Press
www.servergeek.com
"Pekus Cons. e Desenvolvimento" <pekus@REMOVE_pekus.com.br> wrote in message
news:ez****************@TK2MSFTNGP12.phx.gbl...

Hi,

I have seen some developers commenting that a reference variable is 'more
garbage collection eligible' if the programmer set its value to null after
using it, like this:

public void MemberFunction()
{
AnyClass refVar = new AnyClass ();

// Normal use of refVar functionalities

refVar = null;
}

Is it real? Any comment about?

Thanks,

Baccarin.

[Paul E Collins]

"Pekus Cons. e Desenvolvimento" <pekus@REMOVE_pekus.com.br> wrote:

I have seen some developers commenting that
a reference variable is 'more garbage collection
eligible' if the programmer set its value to null
after using it, [...]
Is it real? Any comment about?

References that are still in use can be null for many good reasons, so I'd
hope this isn't the case.

In fact, I suspect that setting the value of a variable at any point says to
the GC, "I am still changing this variable, so I obviously haven't finished
with it."

This is just speculation, though.

P.

[mikeb]

Pekus Cons. e Desenvolvimento wrote:

Hi,

I have seen some developers commenting that a reference variable is 'more
garbage collection eligible' if the programmer set its value to null after
using it, like this:

public void MemberFunction()
{
AnyClass refVar = new AnyClass ();

// Normal use of refVar functionalities

refVar = null;
}

For local variables, the JIT compiler determines where the last use of
that variable is in the method. The JIT marks the reference as dead
after that point, so the GC can collect whatever is referenced by that
local (as long as no other live reference to the object exists).

In other words, in general, setting a reference to null does not help
anything when the reference is maintained in a local variable.
--
mikeb

[Jon Skeet [C# MVP]]

Paul E Collins <fi******************@CL4.org> wrote:

I have seen some developers commenting that
a reference variable is 'more garbage collection
eligible' if the programmer set its value to null
after using it, [...]
Is it real? Any comment about?

References that are still in use can be null for many good reasons, so I'd
hope this isn't the case.

I think there's really a mismatch of terminology here. Variables
themselves aren't garbage collected - objects are. Setting the value of
a variable to null can, in *some* situations, shorten the lifetime of
an object. It can never shorten the lifetime of an actual object.
Usually it's not worth doing though, as the JIT compiler can usually
see when a variable is no longer used even if it is still theoretically
"live".

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Bret Mulvey [msft]]

"Pekus Cons. e Desenvolvimento" <pekus@REMOVE_pekus.com.br> wrote in message
news:ez**************@TK2MSFTNGP12.phx.gbl...

I have seen some developers commenting that a reference variable is 'more
garbage collection eligible' if the programmer set its value to null after
using it....

It's not so much a problem with local variables in a function. What you have
to watch out for is member variables in a class. If you don't set the member
variable to null if it's not needed any more, but the instance of the class
is still being referenced, the memory consumed by the member variable won't
be garbage-collected until the parent object is collectible. In that
situation you would want to be sure to set the member variable to null.

[Jon Skeet [C# MVP]]

Bret Mulvey [msft] <br***@online.microsoft.com> wrote:

"Pekus Cons. e Desenvolvimento" <pekus@REMOVE_pekus.com.br> wrote in message
news:ez**************@TK2MSFTNGP12.phx.gbl...

I have seen some developers commenting that a reference variable is 'more
garbage collection eligible' if the programmer set its value to null after
using it....

It's not so much a problem with local variables in a function. What you have
to watch out for is member variables in a class. If you don't set the member
variable to null if it's not needed any more, but the instance of the class
is still being referenced, the memory consumed by the member variable won't
be garbage-collected until the parent object is collectible. In that
situation you would want to be sure to set the member variable to null.

Do you run into situations frequently? I very rarely end up in the
situation where I know that I don't need *part* of the state of an
object any more, but that the rest of the object is still required.
When I come across situations like that I usually find that a redesign
of the class gets rid of the problem and ends up with a cleaner
solution anywa6y.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Peter N Roth]

I've been away from this ng for a while ~ good to
see you got your MVP, Jon.

--
Grace + Peace,
Peter N Roth
Engineering Objects International
http://engineeringobjects.com
"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...