You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried on:
go: 1.22.x, 1.23.5, 1.23.6
github.com/bytedance/sonic v1.12.2
github.com/bytedance/sonic v1.12.8 (latest at time of writing)
We noticed that we were getting panics running on graviton in aws. Running locally through qemu I see issues with null and newlines inside of json strings when using ConfigDefault.
Running it a few times every so often I get the signal handler problem. Even when it works obviously the index is way out of bounds so clearly a memory issue.
$ GOARCH=arm64 go run main.go
"Syntax error at index 6: control chars in string\n\n\t{\"a\":\"b\nc\"}\n\t......^....\n"
"Syntax error at index 6: control chars in string\n\n\t{\"a\":\"b\nc\"}\n\t......^....\n"
"Syntax error at index 2113627: expect a `,` or `}`\n\n\t{\"a\":\"b\nc\"}\n\t^\n"
$ GOARCH=arm64 go run ./cmd/foo/main.go
"Syntax error at index 6: control chars in string\n\n\t{\"a\":\"b\nc\"}\n\t......^....\n"
"Syntax error at index 6: control chars in string\n\n\t{\"a\":\"b\nc\"}\n\t......^....\n"
fatal: bad g in signal handler
exit status 2
The text was updated successfully, but these errors were encountered:
brennan-airtime
changed the title
Parsing json strings with invalid bytes inside on arm64 causes memory corruption
Parsing json with invalid bytes inside strings on arm64 causes memory corruption
Feb 12, 2025
Tried on:
go: 1.22.x, 1.23.5, 1.23.6
github.com/bytedance/sonic v1.12.2
github.com/bytedance/sonic v1.12.8 (latest at time of writing)
We noticed that we were getting panics running on graviton in aws. Running locally through qemu I see issues with null and newlines inside of json strings when using
ConfigDefault
.Running it a few times every so often I get the signal handler problem. Even when it works obviously the index is way out of bounds so clearly a memory issue.
The text was updated successfully, but these errors were encountered: