Skip to content
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

encoding/json: cause sweep increased allocation count crash on arm64 #36286

Closed
jing-rui opened this issue Dec 27, 2019 · 2 comments
Closed

encoding/json: cause sweep increased allocation count crash on arm64 #36286

jing-rui opened this issue Dec 27, 2019 · 2 comments

Comments

@jing-rui
Copy link

@jing-rui jing-rui commented Dec 27, 2019

What version of Go are you using (go version)?

$ go version
go version go1.14.0 linux/arm64

go1.14.0 is build use commit 22d28a2

Does this issue reproduce with the latest release?

Yes, we use master golang branch commit 22d28a2 without modify.

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/root/go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/lib/golang"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_arm64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build455143019=/tmp/go-build -gno-record-gcc-switches"

What did you do?

We write a program repeatedly unmarshal config.json file on arm64, run 10 process and wait about an hour some process will crash. When we switch to use jsoniter package, no crash occurs after running 3 days.

Reproduce program https://github.com/jing-rui/go-issue-36101

What did you expect to see?

no process crash

What did you see instead?

ref #36101

@agnivade

This comment has been minimized.

Copy link
Contributor

@agnivade agnivade commented Dec 27, 2019

Is this the same as #36101 ? I wonder why do we need a separate issue then ?

@cherrymui

This comment has been minimized.

Copy link
Contributor

@cherrymui cherrymui commented Dec 27, 2019

Let's discuss this in a single place. Closing this as a dup.

Also, I think this is more like a runtime issue than a json issue.

@cherrymui cherrymui closed this Dec 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.