Let's address another GC misconception: that you can divide GC algorithms into "perfectly precise" ones like tracing and "imprecise" ones like reference counting without cycle collection.
-
-
Ah ok, good. I've been scratching my head.
And how does it lead to leaks in JS? -
And btw, I tend to not call it leaks like e.g. in C/C++ where there is truly no path to an allocated block. In GCed world, this cannot happen (unless the GC is broken). What usually happens and what is called leak in GCed runtime is 'memory hoarding'.
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.