How we analyzed and fixed a Golang memory leak

This fix did not address an actual memory leak (i.e., growing heap) in the Go runtime as the headline suggested; it instead was a change in the Go runtime to make Linux cache memory pages less aggressively. The underlying issue still remains, which is that in some cases, Linux isn't evicting cached pages to stay within cgroup memory limits.

I believe this is fixed when cgroup v2 is used.

> If you are using go between 1.12 to 1.15 within containers, you likely want to set GODEBUG=madvdontneed=1. :-)

This setting is default in Go 1.16+, which was published about 1 year ago. They don't mention what version they're using. The last several releases have landed some pretty significant improvements as I recall, maybe this is a good excuse to upgrade the Go release you use to compile your app.