A simple Go error handling pattern led to 54GB memory usage with 65535 errors (opens in new tab)

(gist.github.com)

3 pointsalingse9mo ago1 comments

1 comments

While debugging why our golangci-lint runs in CI were getting randomly killed, I discovered a surprising memory issue in Go's error handling.

The problem occurs when combining many errors using `errors.Join()` and wrapping them with `fmt.Errorf()`. Here's a minimal reproduction

j / k navigate · click thread line to collapse

alingseOP9mo ago

While debugging why our golangci-lint runs in CI were getting randomly killed, I discovered a surprising memory issue in Go's error handling.

The problem occurs when combining many errors using `errors.Join()` and wrapping them with `fmt.Errorf()`. Here's a minimal reproduction

j / k navigate · click thread line to collapse