Circular references in Javascript / Garbage collector

by

Any half-decent garbage collector will handle cycles.

Cycles are only a problem if you do naive reference counting.

Most garbage collectors don’t do ref-counting (both because it can’t handle cycles, and because it’s inefficient). Instead, they simply follow every reference they can find, starting from “roots” (typically globals and stack-based variables), and mark everything they can find as “reachable”.

Then they simply reclaim all other memory.

Cycles are no problem because they just mean that the same node will be reached multiple times. After the first time, the node will be marked as “reachable” already, and so the GC will know that it’s been there already, and skip the node.

Even more primitive GC’s based on reference-counting typically implement algorithms to detect and break cycles.

In short, it’s not something you have to worry about.
I seem to recall that IE6’s Javascript GC actually failed to handle cycles (I could be wrong, it’s been a while since I read it, and it’s been much, much longer since I touched IE6), but in any modern implementation, it is no problem.

The entire point in a garbage collector is to abstract away memory management. If you have to do this work yourself, your GC is broken.

See MDN for more information on modern garbage collection and the mark-and-sweep algorithms that are used.

More Related Contents:

  1. requestAnimationFrame garbage collection
  2. What is JavaScript garbage collection?
  3. Deleting Objects in JavaScript
  4. If a DOM Element is removed, are its listeners also removed from memory?
  5. Memory leak risk in JavaScript closures
  6. How does garbage collection work in JavaScript?
  7. Does never resolved promise cause memory leak?
  8. How to serialize DOM node to JSON even if there are circular references?
  9. About closure, LexicalEnvironment and GC
  10. How JavaScript closures are garbage collected
  11. Finding JavaScript memory leaks with Chrome
  12. Javascript and Garbage collection
  13. Tool to track down JavaScript memory leak
  14. Best practices for reducing Garbage Collector activity in Javascript
  15. Do I need to remove event listeners before removing elements?
  16. How are closures and scopes represented at run time in JavaScript
  17. When should I use delete vs setting elements to null in JavaScript? [duplicate]
  18. Can dynamically loaded JavaScript be unloaded?
  19. How to request the Garbage Collector in node.js to run?
  20. Forcing garbage collection in Google Chrome
  21. QML garbage collection deletes objects still in use
  22. Does JavaScript setInterval() method cause memory leak?
  23. How to remove DOM elements without memory leaks?
  24. Do you know what may cause memory leaks in JavaScript?
  25. How to restore circular references (e.g. “$id”) from Json.NET-serialized JSON?
  26. How to iterate over a WeakMap?
  27. How to profile and get Javascript performance [duplicate]
  28. What’s the best way (most efficient) to turn all the keys of an object to lower case?
  29. Prevent click event from firing when dblclick event fires
  30. Use of require(lib) versus in Electron apps

Leave a Comment