> What you really want is the stack trace for the goroutine that created
the leaking goroutine, at the time that the leak was created.
GODEBUG=tracebackancestors=1 ought to show that. tracebackancestors is new
in Go 1.11 IIRC.
https://golang.org/pkg/runtime/#hdr-Environment_Variables
On Thur
I would point out that this *is *the whole stack trace *of the goroutine*.
In fact, the actual stack trace is just the first line, since the goroutine
in question is only one function deep. If you are breaking into your
program after the leaking has started, then the function that created the
g
If you look at
created by net/http.(*Transport).dialConn
/usr/local/go/src/net/http/transport.go:1117 +0xa35
It shows you that the go routine is created internally - but it is coming from
dialConn() so you need to review all usages of this method. Sometimes when
using 3rd party librari
Have you tried Ctrl+\ ? That should dump all the goroutines. It also closes
the app.
If you don't want the app to shut down, then you can take a goroutine
profile - https://golang.org/pkg/runtime/pprof/#Profile.
On Wednesday, 7 November 2018 09:25:24 UTC+5:30, rickyu...@gmail.com wrote:
>
> I
