Closed stgraber closed 3 years ago
@mdlayher this catches pretty much all errors we're triggering in some aggressive stress testing of LXD.
Excellent!
We have some more issues around this which I'm tracking down, the current one is an occasional connection timed out
error, not really an issue by itself, but when it hits, Go very rapidly starts eating all of the system's memory. According to pprof it's all going into timer.NewTimer
which appears primarily used by Go's net functions.
I'm not sure what's going on there exactly and my reproducer isn't exactly trivial either nor is it quick (takes as long as an hour).
Signed-off-by: Stéphane Graber stgraber@ubuntu.com