I don't think cgo is to blame then, the only cgo used by the http package is
your system's DNS resolver.
--
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-
>
> What cgo calls were those? Are you using an alternative crypto
> implentation?
Sadly, I didn't save any of the metrics I gathered any more, so I can't say
specifically what CGO calls were being used by my application. I do recall
a good bit of the memory being spent on checking the certificat
Also quite curious about this. My assumption was that all resources should
eventually be cleaned up when http.Client goes out of scope?
--
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
What cgo calls were those? Are you using an alternative crypto implentation?
--
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.
Problem resolved. Application was allocating a new http.Client for every
remote call made, and since the handshake ultimately comes down to CGO
calls, I was accumulating memory that was not managed by Go's GC.
On Tuesday, March 14, 2017 at 8:21:58 PM UTC-4, Nathan Morley wrote:
>
> Hello,
>
> So
