sync: using a nil Pool causes a fatal error #61651
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Reproduces with 1.20.6
What operating system and processor architecture are you using (
go env
)?linux/amd64
What did you do?
Run
What did you expect to see?
A panic for a nil pointer dereference.
What did you see instead?
A fatal error because of an unexpected signal during runtime execution.
I'm not sure how important fixing this is. While fatal errors can't be recovered from, this really only struck a nerve with me because of the unexpected error and the full stack trace, which made me look for wrong unsafe code, not a nil sync.Pool.
The text was updated successfully, but these errors were encountered: