|
|
|
|
|
|
by otterley
1552 days ago
|
|
|
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. |
|
|