-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: MSpanList_Insert error using Go 1.7.1 on macOS Sierra #17335
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
Duplicate #17182 |
I see this issue was marked as a duplicate of #17182 and the problem was resolved because of GOBOOTSTRAP error while building the Go distribution. But I am seeing this panic consistently after upgrading to MacOS Sierra and trying to build fuchsia. This panic consistently occurs when the mojom tool tries to generate Go bindings. I am not building a Go distribution at all. The mojom_tool.py is wrapper over the correct binaries, Linux or MacOS, for the mojom tool written in Go. /usr/bin/env ../../mojo/public/tools/bindings/mojom_tool.py gen --src-root-path ../../ -I ../../ -I ../../ --output-dir /Users/shakeel/google/fuchsia/out/debug-x86-64/gen --no-gen-imports --generators legacy,c,go --gen-arg dart_ignore-package-annotations ../../mojo/public/interfaces/bindings/tests/versioning_test_client.mojom runtime stack: goroutine 1 [running]: |
@shakeel try to update or reinstall go |
@shakeel Try to build with -a go build -a ./... After that my executable did not show this error anymore. |
@BoGeM and @sklevenz the mojom tool is precompiled by Google, not sure which version of Go. https://fuchsia.googlesource.com/mojo/public/+/master/tools/bindings/mojom_tool/bin And it looks like most of the developers writing mojo components are on Ubuntu and they are not affected by this defect, it is only on MacOS Sierra |
@shakeel yes, this bug is only on macOS Sierra. |
I reinstalled go latest version on macOS Sierra, then this error did not appear (at least until now) |
I got this error and I solved it removing USB hub. It does not occour if I directly plug the node in the MAC USB. |
I'm getting this error all the time. Less frequently using go 1.3 than 1.8.3 I upgraded to. The only "go" executable I use is the salesforce "force" cli tool. DrozBook:fsb-maintenance tgagne$ uname -a |
@tggagne, that means the saleforce "force" tool needs to be recompiled with the fixed version of Go. |
why is it stochastic ? I see it 1/3 of the time but not all the time. i think it only happens on certain retries or something. |
@jayunit100 this issue is closed. Please open a new issue and complete the template rather than commenting on a closed issue. Thanks. |
@tggagne, I am sure you already fixed this, but for others who may run into the same issue with the force.com cli issue, as bradfitz suggested:
|
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?1.7.1
What operating system and processor architecture are you using (
go env
)?macOS Sierra Version 10.12
GOARCH="amd64"
GOBIN="/Users/d036242/dev/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/d036242/dev/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.1/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/33/7ggkbf316lq01872br8pmjv8ccxxy9/T/go-build804843343=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
We are working with CloudFoundry and using Spiff and Yaml2Json programs written in Go.
https://github.com/cloudfoundry-incubator/spiff
https://github.com/bronze1man/yaml2json
What did you expect to see?
spiff file1.yml file2.yml | yaml2json
Expect to see a json document on stdout.
What did you see instead?
Since update to macOS Sierra both tools mentioned above show this MSpanList_Insert error sometimes. The problem occurs sporadically and is not reproducible. Both tools were re-compiled using Go 1.7.1.
failed MSpanList_Insert 0x464110 0x3c235d63c754c 0x0
fatal error: MSpanList_Insert
runtime stack:
runtime.MSpanList_Insert(0x405990, 0x464110)
/usr/local/go/src/runtime/mheap.c:692 +0x8f
runtime.MHeap_Alloc(0x4040c0, 0x1, 0x10000000014, 0x10409)
/usr/local/go/src/runtime/mheap.c:240 +0x66
runtime.MCentral_CacheSpan(0x40c078, 0x463fd8)
/usr/local/go/src/runtime/mcentral.c:85 +0x167
runtime.MCache_Refill(0x45f000, 0x14, 0x463fd8)
/usr/local/go/src/runtime/mcache.c:90 +0xa0
goroutine 1 [running, locked to thread]:
runtime.switchtoM()
/usr/local/go/src/runtime/asm_amd64.s:198 fp=0xc208059b38 sp=0xc208059b30
runtime.mallocgc(0x160, 0x25e740, 0x0, 0xca67)
/usr/local/go/src/runtime/malloc.go:178 +0x849 fp=0xc208059be8 sp=0xc208059b38
runtime.newarray(0x25e740, 0x1, 0x4791c79b)
/usr/local/go/src/runtime/malloc.go:365 +0xc1 fp=0xc208059c20 sp=0xc208059be8
runtime.mapassign1(0x1f4200, 0xc20803c9f0, 0xc208059d68, 0xc208059da8)
/usr/local/go/src/runtime/hashmap.go:402 +0x109 fp=0xc208059cc0 sp=0xc208059c20
text/template.addValueFuncs(0xc20803c9f0, 0xc20803c9c0)
/usr/local/go/src/text/template/funcs.go:68 +0x447 fp=0xc208059e38 sp=0xc208059cc0
text/template.createValueFuncs(0xc20803c9c0, 0xc20803c9c0)
/usr/local/go/src/text/template/funcs.go:54 +0x50 fp=0xc208059e60 sp=0xc208059e38
text/template.init()
/usr/local/go/src/text/template/funcs.go:49 +0xb91 fp=0xc208059f78 sp=0xc208059e60
github.com/codegangsta/cli.init()
/home/dev/go/spiff/src/github.com/codegangsta/cli/help.go:215 +0x59 fp=0xc208059f90 sp=0xc208059f78
main.init()
/home/dev/go/spiff/src/github.com/cloudfoundry-incubator/spiff/spiff++/spiff.go:193 +0x60 fp=0xc208059f98 sp=0xc208059f90
runtime.main()
/usr/local/go/src/runtime/proc.go:58 +0xe4 fp=0xc208059fe0 sp=0xc208059f98
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:2232 +0x1 fp=0xc208059fe8 sp=0xc208059fe0
The text was updated successfully, but these errors were encountered: