-
Notifications
You must be signed in to change notification settings - Fork 18k
net: panic: runtime error: invalid memory address or nil pointer dereference #32004
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
Like your other bug, I don't see how this can happen. It seems that Can you run with the race detector? /cc @ianlancetaylor |
If the program ran for 100 hours and then crashed, that can only mean that |
@bradfitz @ianlancetaylor, I have ran it in my local machine with race detector enabled, unfortunately it crashed my computer, but after restarted my computer, the terminal output messages are restored, and there is no race detected so far. So, is it possible for data races to cause these panics? |
Yes, it is possible for a data race to corrupt memory and thus to cause an error like this. It's not especially likely but it is possible. |
@ianlancetaylor , I can't say it is unfortunate or fortunate. But after I made a build with cgo enabled and race detector enabled. It have ran more than 50 hours without any data race or panic…… I'm going on with race detector enabled running, wait till the first data race coming out or the first panic occurred. |
This has been in waiting for info for more than 2 years, and it was reported against a version of Go that is no longer supported, so let's archive this. If it comes out again on a recent Go version, we can open a new issue. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Works without panics.
What did you see instead?
This panic is very rarely, tbh it was first time after hundreds hours running. And it maybe linked to #31986 .
The text was updated successfully, but these errors were encountered: