-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: "found bad pointer in Go heap" on darwin/arm64 #32324
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
Another |
Another, this time in the cmd/compile test: https://build.golang.org/log/2a4dfbd156fcf4676e7e745c78219497c463c38f |
Failed at linux/mips64le too https://build.golang.org/log/e93b008016bfe25042e76766bd32eaa749b4b809 |
Should we move this into the Go 1.14 release? @bcmills |
Maybe? I think #35541 is pretty clearly worth investigating, since that's on real hardware, but it's not clear to me that a failure that only occurs on 2019-11-12T05:18:25-194ae32/linux-mips64le-mengzhuo |
Haven't seen any more of these on |
Possibly related to #32026.
Seen in https://build.golang.org/log/581aabff93c4fd2e8fb64339dcbbe37bfedf7985:
The text was updated successfully, but these errors were encountered: