Description
I'm seeing fairly frequent OOM failures in the Go build dashboard.
Some of them look like misconfigured or undersized builders, while others could plausibly be bugs in the runtime (such as #52433). In other cases (such as #49957), it's much less clear what led to the failure.
It would be very helpful to be able to distinguish those cases from the failure logs. Today, we get fatal error: runtime: out of memory
, but generally the runtime doesn't actually tell us how much memory it was using when that happened. (We do get a goroutine dump, but a goroutine dump is only loosely correlated with the size of the heap.)
@golang/runtime: how difficult would it be to have the runtime dump a best-effort summary of heap stats when it hits the out of memory
condition?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status