from Hacker News

A simple Go error handling pattern led to 54GB memory usage with 65535 errors

by alingse on 6/18/25, 2:29 PM with 1 comments

• by alingse on 6/18/25, 2:29 PM

  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