JavaScript(ES6)：将对象设为null时WeakMap的垃圾回收机制

Hey folks, let's break down how JavaScript's WeakMap works—focusing on its key rules, how it taps into garbage collection, and why setting an object to null effectively removes its presence from a WeakMap context.

Core WeakMap Characteristics #

• Only objects allowed as keys: Unlike regular Map, WeakMap refuses primitive values (strings, numbers, booleans) as keys. This restriction is what enables its unique garbage collection behavior.
• Weak references to keys: WeakMap holds weak references to its object keys. In plain terms: if the object key has no other strong references left in your code, the JavaScript garbage collector will automatically clean up that object—and also delete the corresponding key-value pair from the WeakMap. No manual cleanup needed, which makes it ideal for use cases like caching or storing private object metadata.

Why Setting an Object to null Acts Like Deletion #

When you assign an object variable to null, you're severing the strong reference to that object. If no other variables or parts of your code are pointing to it, the garbage collector will mark the object for cleanup. Once that happens, the WeakMap will drop the associated key-value pair automatically—you don't have to call delete() on the WeakMap yourself.

Example Code #

let planet1 = {name: 'Coruscant', city: 'Galactic City'};
let planet2 = {name: 'Tatooine', city: 'Mos Eisley'};
let planet3 = {name: 'Kashyyyk', city: 'Rwookrrorro'};

const lore = new WeakMap();
lore.set(planet1, true);
lore.set(planet2, true);
lore.set(planet3, true);

console.log(lore); // Output: WeakMap {{…} => true, {…} => true, {…} => true}

// Remove the strong reference to planet1
planet1 = null;
// After garbage collection runs, lore will no longer include the planet1 entry

内容的提问来源于stack exchange，提问作者Bruno Mazza