将对象设置为 null 时的 JavaScript（ES6）WeakMap 垃圾回收

Question

I've just read that WeakMaps take advantage of garbage collection by working exclusively with objects as keys, and that assigning an object to null is equivalent to delete it:

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}

Then I set the object equal to null:

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

Why is the output the same? Wasn't it supposed to be deleted so that the gc could reuse the memory previously occupied later in the app? I would appreciate any clarification. Thanks!

Answer 1

Garbage collection does not run immediately. If you want your example to work you need to force your browser to run garbage collection.

Run chrome with the following flag: google-chrome --js-flags="--expose-gc" .

You can now force the garbage collection by calling the global gc() method.

Answer 2

I was trying to figure out the same thing, in 2022, but it looks like the browsers don't bother to garbage collect if the WeakMap is small.

But if you do something like this:

let weakmap = new WeakMap()

for (let i = 0; i < 2000; i++) {
    let john = {meow: i}

    weakmap.set(john, i)
    console.log(weakmap)
    john = null

    let div = document.createElement("div")
    div.innerText = i
    document.body.append(div)
    weakmap.set(div, i)
    div.remove()
}

let john2 = {} // Test to see if it garbage collects this (it shouldn't)

weakmap.set(john2, "random")

console.log(weakmap)

Then the browser will garbage collect after a certain size:

As you can see it went from the size to 4001 too 101. It looks like the browser doesn't bother garbage collecting the rest.