I have a program that appears to be leaking OS threads on ARM (raspberry pi). Watching the number of goroutines using runtime.NumGoroutine() shows that they are staying mostly constant. But ps -eLf shows the number of threads gradually increasing as well as the resident and virtual memory use under constant load.
This does not happen on x86 linux or mac osx using the same code. The pi is running Debian 8. go 1.7.1, 1.7.3 and 1.6.3 give the same results. I pulled out everything that is not 100% native go code thinking that something outside of go in C was causing the leak. The fact that it only happens on ARM is making me think that my code is not the problem. Any ideas where to look next? -- 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.
