-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: fatal error: checkdead: runnable g #63761
Comments
In triage: @prattmic thinks this could be a race with a goroutine exiting, since that goroutine doesn't appear in the stack trace. However, unless this is reproducible, I'm not sure this is enough information to come to a conclusion. |
If you see it again, please report back! Thanks. |
This is complete panic stack trace, goroutine 18322774 is in log file. I hope it can help you analyze |
Ah, thanks. For reference, there are two runnable goroutines in the full dump:
|
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
only once, run 142d in production
What operating system and processor architecture are you using (
go env
)?run application at k8s, docker image from centos7 x86_64 GNU/Linux
go env
OutputWhat did you do?
I didn't do anything,it`s an grpc service,normal running 142d, but get a panic today
What did you see instead?
Below is some panic log, if needed,i can provide complete runtime panic output log
The text was updated successfully, but these errors were encountered: