-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runtime: spurious crashes related to timers in go 1.23.0 #69625
Comments
are you copying timer values and not pointers? we need a reproducer for this to be actionable |
This is a sizeable piece of code. I would not exclude bugs, however it's unlikely that we I am copying timer values, since we're using *time.Timer/*time.Ticker everywhere. the below crashes may be related, although I don't understand how.
|
CC @golang/runtime A fault address like |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Go version
go version go1.23.0 linux/amd64
Output of
go env
in your module/workspace:What did you do?
recompiled go code that has been running fine for a long time.
What did you see happen?
we are experiencing frequent crashes that follow this pattern:
What did you expect to see?
no crash.
The text was updated successfully, but these errors were encountered: