Why Setting Unused Objects to null May Not Help Java Garbage Collection

Many Java developers have heard the advice "assign null to objects that are no longer used" and believe it helps the garbage collector reclaim memory sooner, but the actual reason is often unclear.

The article demonstrates this with a simple program that allocates a large byte array inside an if block, prints its size, and then calls System.gc() . Without assigning null to the array, the GC logs show that the memory usage drops only slightly, indicating the array was not reclaimed.

When the same code explicitly sets placeHolder = null before the System.gc() call, the GC logs show a dramatic reduction to 345 KB, confirming the array was reclaimed.

To understand why, the article examines the JVM runtime stack (the local variable table). Variables are stored in slots; after the if block ends, the slot that held placeHolder remains occupied until another variable reuses it. As long as the slot contains a reference, the GC treats the object as reachable.

By introducing a new variable (e.g., int replacer = 1 ) after the block, the JVM reuses the same slot, effectively discarding the reference to placeHolder . The subsequent GC then successfully frees the memory, demonstrating that slot reuse achieves the same result as assigning null .

The article also explains that the JVM’s local variable table is fixed at compile time, and the reachability analysis algorithm determines object liveness based on references from the stack, static fields, and other roots.

In conclusion, while setting unused references to null can work, it should not be treated as a universal rule; understanding the JVM’s stack behavior and allowing slot reuse is a more reliable way to aid garbage collection.

Reference: Zhou Zhimin, Deep Understanding of the Java Virtual Machine , Mechanical Industry Press, 2013.