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 libraries it is easier to set a breakpoint and run under the
debugger to see the actual creation call stack.
It is a limitation of the Go design IMO - go routines are very easy to create
and use - so often you might end up with thousands with no real good tools to
manage/monitor them.
There are some third party packages that attempt to provide this
monitoring/management layer, but there are many - tough to pick one - which is
why I think it needs to be moved into the core, so standardization and
improvements are easier to handle. But just my 2 cents.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
