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: slice bounds out of range in issue9321 and issue9714 #16757
Comments
Does your program have any data races? |
No warnings on |
Sorry if you did this already, but you need to run it with the race detector just build it:
or
|
Sorry, it should have been obvious that the race detector works at runtime. I have left my program running for 5 minutes with no |
Left it running for 16 hours: no data race warnings came up. We're currently working around this by deferring a recover in all goroutines that buffer. |
Is the code available? |
Sorry @bradfitz, the code is private. I may take some time to reproduce this issue without internal code in the future, but not anytime soon. I know this is insufficient information to debug at this point, but I wanted to make sure you all know that this can happen in go1.6.2, since #9714 implied a belief that this was fixed in go1.5. |
I guess we'll have to close this bug, then, since there's nothing to do. I still strongly suspect a race due to misuse of the easy-to-misuse Please file a bug again or reopen this one if you have a minimal repro with source code. |
Version, OS, architecture:
go version go1.6.2
linux-amd64
What happened: slice bounds out of range in
bytes.Buffer.grow
when we callbytes.Buffer.WriteString
with buffered output fromexec.Command
. Unfortunately, I don't have repro steps, but we have seen this a dozen times spread across different machines, so it seems that #9714 still happens in go1.6.2.Expected: either successfully write the string to the
bytes.Buffer
or panic withErrTooLarge
.Actual: panic with slide bounds out of range
Sorry if this duplicate issue isn't the correct SOP: couldn't find any docs on working with
FrozenDueToAge
.The text was updated successfully, but these errors were encountered: