-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: fatal error: MSpanList_Insert #17492
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 also encountered this problem when I first compile. Building compilers and Go bootstrap tool for host, darwin/amd64.lib9 runtime stack: goroutine 1 [running]: goroutine 5 [syscall]: |
Which version of OS X / macOS are you running? See https://github.com/golang/go/wiki/Darwin. If you are running macOS 10.12 Sierra, you need to use the latest version of Docker including Go 1.7.1 runtime. |
@xing00lian, your issue is #16352. The Go 1.4 branch doesn't compile on Sierra at the moment. |
@bradfitz 10.12 Sierra Unfortunately, I have to use an old Docker build for my dev env. How does Docker affect the Go runtime? |
macOS Sierra changed how you fetch the time from the system. Programs built with Go need to be recompiled to Go 1.7+ to work on Sierra. That includes Docker, since Docker is written in Go. |
Wow, I can't believe they made such a big breaking change! Thanks. |
See #17490 |
Mac OS Sierra has backwards-incompatible changes that require using a newer version of go with Sierra suppport. See golang/go#17492 (comment)
… referenced mongo version to V3_4 to fix intermittent problem running tests on OS X Sierra. From flapdoodle-oss/de.flapdoodle.embed.mongo#190 : ... under current macOs Sierra mongodb 3.2 does not function that well - mongotools (like mongorestore) are built with go 1.4.2 and macOs Sierra had some breaking changes (see golang/go#17492 )
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
Ran docker:
Docker version: Docker version 1.7.1, build 786b29d
What did you expect to see?
Normal help output.
What did you see instead?
Comments
I've seen this panic numerous times on this computer, but it doesn't repro consistently, just kind of randomly.
The text was updated successfully, but these errors were encountered: