Great writeup!
Does this mean, that where ever we have circular references, the values will never be garbage collected? Is there any workaround to this, AFAIK we don't have control over the garbage collector in JS?
All modern browsers have a mark and sweep garbage collector. Javascript has come up with ways to improve garbage collection such as:
parallel collection - where the main javascript thread has multiple helper threads
help in garbage collection.
incremental collection - all collection is carried by the main thread but in
intermittent stages.
concurrent collection - main thread runs javascript code uninterrupted and all garbage collection is done by helper threads. (I should add an article on this)
and this means that circular references are no longer a problem. Yes, we don't have control over garbage collection as there is no form of manual garbage collection.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great writeup!
Does this mean, that where ever we have circular references, the values will never be garbage collected? Is there any workaround to this, AFAIK we don't have control over the garbage collector in JS?
All modern browsers have a mark and sweep garbage collector. Javascript has come up with ways to improve garbage collection such as: