-
Notifications
You must be signed in to change notification settings - Fork 18k
fatal error: unexpected signal during runtime execution #32694
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
Comments
Please provide a way to reproduce the panic by posting or linking to the code and how it was started. |
This looks kinda like there's a non-Go function on the Go stack. Are you using assembly? |
@randall77 I don't have any assembly, only go code. |
Hello @chaitanyav - We would need some way to reproduce this error to investigate further. As mentioned above, please provide us with the code that is triggering this if possible. Otherwise, we need more information on what triggers the crash. Can you pinpoint to a part of the code, which, if removed prevents the crash ? Is the crash deterministic ? |
This happened only once, on a perpetually running process which spawns goroutines (number of CPU cores on the system) every few minutes. This program has no race conditions. |
Thanks. If this has happened only once, and if we don't have any code to reproduce, it will be very hard to investigate this. If at all you cannot provide us with code, I would request you to run your application with |
@agnivade Sure will update the issue when I encounter it again. |
Closing this issue, might be a regression in the code. Have not seen it happen again. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I have not tried my program with 1.12.6.
What operating system and processor architecture are you using (
go env
)?This is CentOS release 6.8 (Final).
go env
OutputWhat did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: