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

base64x use avx2 simd cause panic #330

Open
liuq19 opened this issue Nov 15, 2022 · 0 comments
Open

base64x use avx2 simd cause panic #330

liuq19 opened this issue Nov 15, 2022 · 0 comments
Labels
low-priority Low priority issue, deal with it later

Comments

@liuq19
Copy link
Collaborator

liuq19 commented Nov 15, 2022

use avx2 mode in base64

const (
    _MODE_JSON = (1 << 3) | (1 << 2) // base64 mode
)

test command:

go test -run=TestIssue213$  -count 100 -v  > debug.out 

output:

Begin GC looping...
=== RUN   TestIssue213
--- PASS: TestIssue213 (0.03s)
=== RUN   TestIssue213
--- PASS: TestIssue213 (0.00s)
=== RUN   TestIssue213
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0xb01dfacedebac1e pc=0x102410b]

runtime stack:
runtime.throw({0x13a029a, 0x80c004779fff})
	/Users/bytedance/goroot/go1.17/src/runtime/panic.go:1198 +0x71
runtime.sigpanic()
	/Users/bytedance/goroot/go1.17/src/runtime/signal_unix.go:719 +0x396
runtime.(*sweepLocked).sweep(0x293305b8, 0x0)
	/Users/bytedance/goroot/go1.17/src/runtime/mgcsweep.go:436 +0x12b
runtime.(*mcentral).uncacheSpan(0x104e5c6, 0x70000c064e80)
	/Users/bytedance/goroot/go1.17/src/runtime/mcentral.go:223 +0
@liuq19 liuq19 added the low-priority Low priority issue, deal with it later label Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-priority Low priority issue, deal with it later
Projects
None yet
Development

No branches or pull requests

1 participant