What happens to WeakMap entries when JavaScript's garbage collector runs?
During garbage collection: 1) The collector identifies objects that are no longer referenced elsewhere, 2) WeakMap entries whose keys are among these objects are automatically removed, 3) This process is transparent and cannot be observed directly, 4) The timing of collection is determined by the JavaScript engine, 5) This behavior is what makes WeakMap 'weak' - it doesn't prevent garbage collection, 6) The process is part of the regular garbage collection cycle, 7) This automatic cleanup is key to WeakMap's memory management benefits, 8) Understanding this behavior is crucial for proper WeakMap usage.