Memory leak in retrier implementation

[hummerd]

We've noticed that in case of use retry policy our services start consume more and more memory that is not freed with time. We have services that makes about 5000 http requests per minute and it makes 9 hours for service to reach memory limit in 60 MB (this is our memory limit in k8s for that service). Without retry policies service not consuming additional memory - it's memory usage stays constant with time.

Golang's pprof shows that objects inuse are not canceled contexts.

I think that the problem is in RoundTrip method. It creates context that in case of successful call will never be canceled and therefore will never be garbage collected. Same goes for RetryAfter implementation. Linter wasn't joking.