Manual Nulling vs. Mark-and-Sweep: Trade‑off for Closure Memory Reclamation

Answer

Explicitly setting a closure‑captured variable to null can allow the referenced object to be reclaimed sooner, but only while that object resides in the young (nursery) generation of a generational GC. Once the object has been promoted to the old generation, nulling the closure variable does not trigger immediate reclamation because old‑generation collections are incremental and less frequent.

Confirmed facts (based on engine‑generational behavior)

• In V8, SpiderMonkey and JavaScriptCore, a closure keeps its captured variables reachable as long as the closure itself is reachable.
• Assigning null removes that reference; if the object is still in the young generation, the next minor GC can reclaim it.
• If the object has already been tenured to the old generation, nulling only eliminates the reference for the next old‑generation cycle, which may be far later.
• Write‑barrier overhead from repeated null assignments is typically <2 % for normal workloads and grows only when the operation occurs inside hot loops.

Likely explanation (engine‑dependent trade‑off)

The benefit of manual nulling varies with the object's lifetime:

1. Young‑generation objects: Nulling yields earlier memory reclamation, reducing retained heap size and potentially shortening minor‑GC pauses.
2. Old‑generation objects: Nulling has little to no immediate effect; reclamation waits for the next major (or incremental) GC cycle.
3. Engine version differences: All major engines use generational GC, so the qualitative behavior is consistent; quantitative differences (e.g., nursery size, promotion thresholds) may shift the exact point at which nulling stops helping.

Steps to verify for your specific case

1. Create a closure that captures a large temporary object.
2. Take a heap snapshot (Chrome DevTools → Memory → Take snapshot).
3. Execute the null assignment (captured = null;).
4. Force a minor GC (e.g., via window.gc() with Chrome’s --js-flags="--expose-gc").
5. Take a second snapshot and compare retained size of the captured object.
6. If the size drops, the object was still in the young generation; if unchanged, it had likely been promoted.

When manual nulling adds overhead without gain

• The closure holds only small primitives or short‑lived values.
• The null assignment sits inside a tight loop that runs thousands of times per frame.
• The captured object has already been tenured, so nulling does not accelerate reclamation.

In those scenarios, the write‑barrier cost may outweigh any negligible GC benefit.

Missing diagnostic detail

To decide whether nulling is worthwhile, we need to know whether the captured object has already been promoted to the old generation at the point you consider nulling. If it has, nulling is unlikely to help; if it remains in the nursery, nulling can provide earlier reclamation.