Erlang gets away with no global pauses because there is no shared state [1] between Erlang processes (their term for fiber). Loom/JVM fibers doesn't impose the

Erlang gets away with no global pauses because there is no shared state [1] between Erlang processes (their term for fiber). Loom/JVM fibers doesn't impose the same limitation; references can be shared across threads. So I would expect that, without a concurrent collector, you'd encounter global pauses. [1] outside of some special case, natively implemented datastructures