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
File descriptor slice bounds out of range error #30330
Comments
Something is wrong with the slice passed to |
@ianlancetaylor thanks for the response and for catching that, I should have tried harder to decode the stack trace myself. That's really strange, since I'm not doing anything out of the ordinary to get the byte slice I pass to
That |
Thanks. I don't have an explanation. I recommend 1) run your program under the race detector; 2) see if this problem happens again. |
Will do, thanks a lot. I'll call this a hardware issue and close the issue for now, and reopen if I can reproduce with the race detector. |
FWIW there were no data races and I wasn't able to reproduce it 🤷♂️. Weird. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, I'm running the latest release.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Wrote a program that fires off one HTTP request and writes one file for each of ~200,000 entries.
What did you expect to see?
I expected to be able to write a JSON blob to a file with
ioutil.WriteFile
.What did you see instead?
After about 100,000 entries (so 100k HTTP requests and 100k written files), I got a panic. I wasn't out of storage or file descriptors. This was running on an XFS filesystem. I wish I could reproduce this but after running the program again I am unable to, and I can't share the source here.
The text was updated successfully, but these errors were encountered: