-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: 1.5.1 compiler crashed with "unswept span" #13609
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
@omerkirk Go 1.5.2 was released recently. Can you please check to see if the crash occurs with Go 1.5.2 ? |
@davecheney I have been using go for almost 2 years now and this is the first I have encountered an issue like this. And I am not really sure how to reproduce it. We have 5 active high-load web services running on go 1.4.2 without issues. Since we started using 1.5.1 we are experiencing regular crashes related to cgo. I will try with 1.5.2 and update the issue if there are anymore issues. |
@omerkirk, the issue you reported was a compiler crash. If you are also having issues with cgo under go 1.5.1, would you please log a separate issue as the compiler does not use cgo, so the issues are unrelated.
|
@davecheney the compiler issue we encountered was after our app crashed due to cgo. That is why I referred to it. Now that I read it again I didn't make it clear sorry about that. I am planning to open a seperate issue about the crashes we are seeing related to cgo. |
The compiler crash reported here is not connected to whatever cgo problems you have been having. Have you seen this compiler crash more than once? |
CC @aclements to see if crash might have been fixed in 1.5.2 or tip. |
@ianlancetaylor This is the first time we had this compiler issue. The only connection is that it happened after our app crashed because of cgo. As I said that is the only reason I referred to cgo, I don't think they are related also. We are now using go 1.5.2 and will update the issue if we see it again. |
This line is saying that the global sweep generation is 8 and the bad span's sweep generation is 136. Since the sweep generation is monotonic, this suggests general memory corruption to me, and not anything specifically related to sweeping. We did fix some memory corruption issues in Go 1.5.2 (specifically relating to non-atomic pointer writes), so this could be fixed. |
I'm going to close this for now, but please reopen if you have a way to reproduce the problem. |
I deployed the same code to two of our servers. These two servers have the same OS (Centos 6.7) and the same kernel (2.6.32-573.8.1.el6.x86_64). However they have different configurations like RAM and CPU.
The code I deployed was working on these servers, however we found a bug and introduced a small fix. One of our servers built the code without issues however on our other server
go build
panics and produces the following output. I had to reboot the server to be able to build the source.It looks like the garbage collector didn't shutdown properly with the app. The app crashed and that is why we had to introduce a fix, however I expect go to cleanup after a crash.
We use go version 1.5.1 and here is my
go env
outputPlease let me know if there is any other info you need to understand the issue.
Panic Stacktrace for go build:
The text was updated successfully, but these errors were encountered: