How setting an Object to null help Garbage Collection?

I was reading through some forums and found suggestion that setting an object to null helps Garbage collection? Is it true. How does it matter for GC whether a reference is already set to NULL or not, GS has to still do its check on the reference right??

Any insight? Does it depend on the GC algorithm ?

I don't know about many GC algorithms though, but I think setting an unused object reference to NULL explicitly should help any GC algorithm as it is going to save some effort for it.

But it can create problem for GC if a program sets a object to NULL and later re-reference it. Read more about GC here...Garbage Collection

____________________________________________
Software Wiki | Interview FAQs | Lucene Search | Oracle | ORM | Struts2 | Job Seeker

I think you misunderstood.

Actually the garbage collector checks if an Object has any reachable reference in any threads. If it has then the Object is not garbage collected.

And about setting the Object to null..See this example

code:

Quote:

---

class GarbageTry
{
public void finalize()
{
System.out.println("Destroyed...");
}
public static void method()
{
GarbageTry obj = new GarbageTry(); //(1)
System.out.println("Sleeping");
try
{
System.gc();
Thread.sleep(5000); //pause to simulate some long processing
}
catch(Exception e)
{}
System.out.println("Woken");
}
public static void main(String[] args)
{
method(); //(2)
try
{
System.gc();
Thread.sleep(5000); //pause so that the object is garbage collected before execution ends.
}
catch(Exception e)
{}
}
}

---

In this code the object will be destroyed after the call at (2) returns. So the memory occupied by the object created at (1) remains occupied for no reasons. To avoid this change this program to-

code:

Quote:

---

class GarbageTry
{
public void finalize()
{
System.gc();
System.out.println("Destroyed...");
}
public static void method()
{
GarbageTry obj = new GarbageTry(); //(1)
obj = null; //(x)
System.out.println("Sleeping");
try
{
System.gc();
Thread.sleep(5000); //pause to simulate some long processing
}
catch(Exception e)
{}
System.out.println("Woken");
}
public static void main(String[] args)
{
method(); //(2)
try
{
System.gc();
Thread.sleep(5000); //pause so that the object is garbage collected before execution ends.
}
catch(Exception e)
{}
}
}

---

The addition of (x) will make the object eligible for garbage collection before the call to sleep. So the object can be destroyed anytime during the execution of the method().

____________________________________________
Priya,
Cooking is Fun | Eat Healthy Stay Fit | Sweets | Raita | Bread | Dal

You don't "set an Object to null". When you do var = null, what you are doing is "erasing", or removing, that reference to the Object. The Object itself still exists, but that reference to it no longer does. Once all references to an Object are removed, it will be Garbage Collected.