[go-nuts] panic in http transport (send on closed channel)

Hi Everyone,

I hope this isn't a duplicate issue but:

I have a number of goroutines that each download a url. After a certain
cutoff point (a timeout), main code execution moves on, leaving goroutines
that didn't finish basically hanging.

See: http://play.golang.org/p/OlPuERL2kQ

Doing this, I'm getting:
net/http.(*persistConn).writeLoop(0xc208351810)
         /root/.gvm/gos/go1.4rc2/src/net/http/transport.go:945 +0x41d
created by net/http.(*Transport).dialConn
         /root/.gvm/gos/go1.4rc2/src/net/http/transport.go:661 +0xcbc
panic: send on closed channel

I found an SO that suggests that resp.Body is probably causing the issue:
http://stackoverflow.com/questions/25152030/panic-in-golang-http-client-with-high-concurrent-excecutions
But the SO doesn't specify the best way to fix this.

Is reading resp.Body the likely source of error?
What would be the best way to handle this?

Thanks,
Aki