Does the machine (vm, container, etc) you are running this application have any swap configured.
What I think is happening is the momentary spike in potential memory usage during the fork / exec cycle is causing the linux memory system to refuse to permit the fork. There are several open issues for this, search clone or vfork on the github.com/golang/go project, but the short version is; add swap. On Friday, 2 June 2017 10:41:10 UTC+10, Dmitry Mishin wrote: > > Hello all, > > Trying to fix the out of memory issue in my go app. > > The app is working fine with no memory usage increasing for 10-15 minutes, > then suddenly system starts giving "cannot allocate memory" error for any > command, same in the app. > > I attached the trace and heap during the out of memory state > > The app is finding files and folders in lustre mount, submitting those as > amqp messages, and copying the discovered files > > Thanks for your help! > -- 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.
