Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
math/rand: index out of range in (*rngSource).Int63 #21099
I'm not sure if reporting this is useful as I can't replicate this at all. Maybe it was just a cosmic ray or maybe someone can use the stack trace to find some obscure bug.
What version of Go are you using (
The out-of-bounds must be on
So when we use them to access the vector, both
Considering you can't reproduce this, it smells like memory corruption (possibly caused by a data race).
I didn't look at the code yet but I agree that it shouldn't be possible to have an out-of-bounds panic here.
I don't think it's in a data race in our process as that would normally make it happen much more of then than this once in a year.
This was on a Google Compute instance which wasn't doing anything else. Not sure how susceptible these are to memory corruptions from something else but I guess it can happen.
It's also possible that the memory corruption was caused by a bug in the Go runtime.
This issue, thought, as it is, it's not actionable: the stack trace tells us nothing, and you can't reproduce the crash, so we cannot use your report to extract a reproducer for a (possible) runtime bug.
Leaving this open in case someone else want to say something about this.