Usually if it is hung doing an allocation, that means that the STW cannot complete, which means some go routine is in a tight loop no yielding to the scheduler.
The only other possibility (I would think) is if you placed a cap on the memory size of the process, and it is trying to allocate but cannot get any more memory for the OS, so it keeps trying to GC to free some memory - but this seems doubtful. > On Dec 14, 2018, at 7:27 PM, Eric Hamilton <e...@kasten.io> wrote: > > I've captured a trace-- I don't yet have much experience with "go tool > trace", but certainly looks to me like it's hung doing an allocation and that > interferes with STW. > > I've attached the trace. Any thoughts? Should I open an issue? > > Thanks, > Eric > > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > <tracefile.23-50-04> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
