Erlang's threads (called processes in Erlang) don't observably share data, so "concurrent" GC is basically a stop-the-world GC on a thread's local heap. There m

Erlang's threads (called processes in Erlang) don't observably share data, so "concurrent" GC is basically a stop-the-world GC on a thread's local heap. There might be some thread synchronisation involved, but I assume it's much simpler to implement, because you don't have to deal with mutability.