> Go garbage collector requires that all threads are stopped when running a collection and that memory must be in a consistent state.
People often ask about how Go differs from Erlang. That one's a fairly large difference under the hood. Erlang does GC on a per process (Erlang process, not OS process) basis.
https://code.google.com/p/go/issues/detail?id=543
Also, from the article:
> Go garbage collector requires that all threads are stopped when running a collection and that memory must be in a consistent state.
People often ask about how Go differs from Erlang. That one's a fairly large difference under the hood. Erlang does GC on a per process (Erlang process, not OS process) basis.