News for hackers. Stuff that matters.
Re:How we analyzed and fixed a Golang memory leak by otterley on Wednesday March 23, 2022 @10:05PM (#30785726)
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.

Re:How we analyzed and fixed a Golang memory leak by sharva on Thursday March 24, 2022 @12:00AM (#30786268)
yeah that's a good point