Why Setting Unused Objects to null Can Actually Help Java GC – A Deep Dive

Preface

Many developers believe that assigning null to objects that are no longer used helps the garbage collector (GC) reclaim memory earlier, but the real reason is often unclear. This article clarifies the actual impact of this practice using JVM examples.

Example Code

Consider a simple program that allocates a large byte array inside an if block and then calls System.gc():

public static void main(String[] args) {
    if (true) {
        byte[] placeHolder = new byte[64 * 1024 * 1024];
        System.out.println(placeHolder.length / 1024);
    }
    System.gc();
}

The array is created in the if scope, but after the block the reference still exists on the stack, so the GC does not reclaim it:

65536
[GC 68239K->65952K(125952K), 0.0014820 secs]
[Full GC 65952K->65881K(125952K), 0.0093860 secs]

When the reference is explicitly set to null before the GC call, the memory is released:

public static void main(String[] args) {
    if (true) {
        byte[] placeHolder = new byte[64 * 1024 * 1024];
        System.out.println(placeHolder.length / 1024);
        placeHolder = null;
    }
    System.gc();
}

65536
[GC 68239K->65952K(125952K), 0.0014910 secs]
[Full GC 65952K->345K(125952K), 0.0099610 secs]

Runtime Stack

Typical Runtime Stack

Local variables are stored in the stack as slots. For example, the following method uses three integer slots:

public static void main(String[] args) {
    int a = 1;
    int b = 2;
    int c = a + b;
}

The stack layout can be visualized as:

Index

Variable

1

a

2

b

3

c

Java Stack Optimization

After the if block finishes, the slots for a, b, and c are no longer needed and can be reused. Reusing slot 1 for a new variable d saves stack space.

Index

Variable

1

a

2

b

3

c

1

d

Note

In the JVM these structures are called the "local variable table" and "slot". The table is fixed at compile time.

A Glimpse at GC

GC determines object liveness by tracing from GC roots, which include objects referenced from the stack. If an object is not reachable from any root, it is considered dead and can be reclaimed.

Note

The algorithm is called "reachability analysis".

JVM "Bug"

When the if block ends, the reference to placeHolder remains in the stack, so System.gc() treats it as live. Introducing another variable that reuses the same slot or assigning null breaks the link, allowing the GC to reclaim the memory.

public static void main(String[] args) {
    if (true) {
        byte[] placeHolder = new byte[64 * 1024 * 1024];
        System.out.println(placeHolder.length / 1024);
    }
    int replacer = 1; // reuses the slot
    System.gc();
}

65536
[GC 68239K->65984K(125952K), 0.0011620 secs]
[Full GC 65984K->345K(125952K), 0.0095220 secs]

Thus, explicitly setting a variable to null or letting another variable reuse its slot achieves the same effect.

Conclusion

Manually assigning null to unused objects can help GC in specific cases, but it should not be treated as a universal rule. Understanding JVM stack slots and reachability analysis is key to using this technique wisely.