The example goroutine in the original post is parked waiting for some other
goroutine to finish up the GC cycle. Somewhere, a goroutine is getting
stuck trying to finish it up, which could possibly be a deadlock. (I am
especially suspicious of a deadlock bug because most threads are stopped
the
I am pretty sure runtime is supposed to crash the process if it slows the
allocators “too much” (I believe there are some config settings to control
this).
If you have enough Go routines it may look like they are hung - you need to
track specific routines by their ID. The stack certainly looks
That's an interesting idea, I probably wouldn't have thought of that on my
own. Is that expected behavior for memory pressure on Windows+golang? I
don't have much windows experience, so my assumption would be that the
Windows equivalent of the OOMKiller would kick in and just kill the
applicati
