I run into this problem now. How do you solve it? On Friday, October 24, 2014 at 3:52:27 AM UTC+8, James Bardin wrote: > > > > On Thursday, October 23, 2014 3:23:48 PM UTC-4, Vincent Batts wrote: >> >> From my experience, it is due to the duplicate instances of >> http.Transport. By default keeps around idle connections for resuse, so it >> is not tagged for garbage collection once its immediately out of scope. The >> Work around is to set DisableKeepAlive to true. >> > > Not sure if you intended to respond to me or not, but the version I was > experimenting with was sing a single instance if Transport and Client and > set DisableKeepAlive to true. >
-- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/2460a0ac-c62a-435c-9a1a-b509348e9326%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
