-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
arm64: fatal error: found bad pointer in Go heap #33446
Comments
Seems like same issue as #21568.. But reproducible on latest available release.. Please suggest. This is a blocker for us. |
Hi, can you tell us what did you do ? Or is there any way we can reproduce this error ? |
@erifan we were testing file uploads using minio. Started minio server(which was built using the above go version) on arm64. |
This error indicates some sort of memory corruption. By far the most common causes are incorrect uses of Can you give us complete and precise instructions for how we can reproduce the problem? Thanks. |
Encounter the same problem while uploading file, crash every few days. go version go1.12.9 darwin/amd64 build.sh server info My go program is a http server, it receives file posted by a http client and then send it to a file server(seaweedfs), this program crash every few days. fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?) runtime stack: runtime: nelems=170 nalloc=61 previous allocCount=60 nfreed=65535 goroutine 3 [running]: |
Thanks for reproducing this issue @FU100 - would you mind sharing main.go? |
@FU100 Unless you are running the same program, this is extremely unlikely to have the same cause as the original report on this issue. Please open a new issue. Thanks. As noted above, the most likely causes of this kind of error are incorrect uses of unsafe.Pointer, incorrect uses of cgo when calling C code, and incorrect C code. In the new issue, please give us complete and precise instructions for how we can reproduce the problem. Thanks. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?The text was updated successfully, but these errors were encountered: