-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: fatal error: bad map state #11838
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
I don't see how this is possible unless there is some memory corruption. |
CC @RLH @aclements |
This has happened a total of twice on the builders, both times on nacl: 2015-07-05T03:52:56-cc3f031/nacl-arm-cheney |
Never mind about 2015-07-05T03:52:56-cc3f031/nacl-arm-cheney. It looks like that dumped the entire contents of some Go binary, which of course contained this error string. |
Can reproduce quite easily in nacl/amd64p32. Cannot reproduce on nacl/386, nor on linux/386, nor on linux/amd64. Reproduces even with gcstoptheworld=1,gcshrinkstackoff=1, suggesting that maybe it is a liveness bitmap problem. |
CL https://golang.org/cl/12971 mentions this issue. |
See http://build.golang.org/log/2b7d4e774fad87aea6381dbfc940a0fae573c6dd.
The text was updated successfully, but these errors were encountered: