caddy-s3-proxy
caddy-s3-proxy copied to clipboard
high cpu after 32 days with caddy-s3-proxy
https://github.com/caddyserver/caddy/issues/5647
pprof output debug
pprof output heap
I'm seeing something similar to this as well as OOM killing of the Caddy process. A quick glance at the code and it's not closing the Body of its S3 responses, which are just plain http.Response structs (if you dig deep enough into the SDK). My guess is that it's leaking memory. Preparing and testing a patch to see if this is the case.