Yeah I don't think that's generally a problem for JS engines because of the incremental garbage collector.
replyIf you make all your memory usage patterns possible for the incremental collector to collect, you won't experience noticeable hangups because the incremental collector doesn't stop the world. This was already pretty important for JS since full collections would (do) show up as hiccups in the responsiveness of the UI.
Interesting, thanks for the info, I'll do some reading on what you're saying. I agree, you're right about JS having issues with hiccups in the UI due to scheduling on a single process thread.
replyMakes a lot of sense, cool that the garbage collector can run independently of the call stack and function scheduler.