dgraph-io / badger

Fast key-value DB in Go.

Home Page:https://dgraph.io/badger

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG]: Panic, help!

caitou2019 opened this issue · comments

What version of Badger are you using?

"github.com/dgraph-io/badger/v4"

What version of Go are you using?

GOROOT="/Users/qyt/go/go1.20.2"

Have you tried reproducing the issue with the latest release?

None

What is the hardware spec (RAM, CPU, OS)?

Linux localhost 4.9.38-bm1684-v10.5.0 #25 SMP Mon Jan 8 15:56:04 CST 2024 aarch64 GNU/Linux

What steps will reproduce the bug?

[06:29:59]unexpected fault address 0x7d18d88000
[06:29:59]fatal error: fault
[06:29:59][signal SIGBUS: bus error code=0x2 addr=0x7d18d88000 pc=0xe00040]
[06:29:59]
[06:29:59]goroutine 231851 [running]:
[06:29:59]runtime.throw({0x243f9b9?, 0x0?})
[06:29:59] /opt/go/src/runtime/panic.go:1047 +0x40 fp=0x7cbfed6c90 sp=0x7cbfed6c60 pc=0xdc9830
[06:29:59]runtime.sigpanic()
[06:29:59] /opt/go/src/runtime/signal_unix.go:834 +0x90 fp=0x7cbfed6cd0 sp=0x7cbfed6c90 pc=0xde0ed0
[06:29:59]runtime.memmove()
[06:29:59] /opt/go/src/runtime/memmove_arm64.s:173 +0x190 fp=0x7cbfed6ce0 sp=0x7cbfed6ce0 pc=0xe00040
[06:29:59]github.com/dgraph-io/badger/v4.(*valueLog).write.func2(0x7c3a1f70e0?)
[06:29:59] /home/jenkins/go/pkg/mod/github.com/dgraph-io/badger/v4@v4.1.0/value.go:828 +0x144 fp=0x7cbfed6d30 sp=0x7cbfed6ce0 pc=0x194e7b4
[06:29:59]github.com/dgraph-io/badger/v4.(*valueLog).write(0x7c3c916af8, {0x7c45eda870?, 0x1, 0x0?})
[06:29:59] /home/jenkins/go/pkg/mod/github.com/dgraph-io/badger/v4@v4.1.0/value.go:886 +0x5bc fp=0x7cbfed6e90 sp=0x7cbfed6d30 pc=0x194e46c
[06:29:59]github.com/dgraph-io/badger/v4.(*DB).writeRequests(0x7c3c916900, {0x7c45eda870?, 0x1, 0xa})
[06:29:59] /home/jenkins/go/pkg/mod/github.com/dgraph-io/badger/v4@v4.1.0/db.go:813 +0x80 fp=0x7cbfed6f40 sp=0x7cbfed6e90 pc=0x19153b0
[06:29:59]github.com/dgraph-io/badger/v4.(*DB).doWrites.func1({0x7c45eda870?, 0xfe2ac0?, 0x7f2e24f940?})
[06:29:59] /home/jenkins/go/pkg/mod/github.com/dgraph-io/badger/v4@v4.1.0/db.go:885 +0x40 fp=0x7cbfed6fa0 sp=0x7cbfed6f40 pc=0x19160a0
[06:29:59]github.com/dgraph-io/badger/v4.(*DB).doWrites.func3()
[06:29:59] /home/jenkins/go/pkg/mod/github.com/dgraph-io/badger/v4@v4.1.0/db.go:938 +0x38 fp=0x7cbfed6fd0 sp=0x7cbfed6fa0 pc=0x1916028
[06:29:59]runtime.goexit()
[06:29:59] /opt/go/src/runtime/asm_arm64.s:1172 +0x4 fp=0x7cbfed6fd0 sp=0x7cbfed6fd0 pc=0xdff5e4
[06:29:59]created by github.com/dgraph-io/badger/v4.(*DB).doWrites
[06:29:59] /home/jenkins/go/pkg/mod/github.com/dgraph-io/badger/v4@v4.1.0/db.go:938 +0x124
[06:29:59]
[06:29:59]goroutine 1 [chan receive, 267 minutes]:
[06:29:59]runtime.gopark(0x7f281cdc40?, 0x10?, 0x10?, 0x0?, 0x2157940?)
[06:29:59] /opt/go/src/runtime/proc.go:381 +0xe0 fp=0x7f28519940 sp=0x7f28519920 pc=0xdcc520
[06:29:59]runtime.chanrecv(0x7f28042360, 0x0, 0x1)
[06:29:59] /opt/go/src/runtime/chan.go:583 +0x468 fp=0x7f285199d0 sp=0x7f28519940 pc=0xd98758
[06:29:59]runtime.chanrecv1(0x7f2841a000?, 0x7f2f4bac00?)
[06:29:59] /opt/go/src/runtime/chan.go:442 +0x14 fp=0x7f28519a00 sp=0x7f285199d0 pc=0xd982b4
[06:29:59]github.com/gogf/gf/net/ghttp.(*Server).Run(0x7f2841a000)
[06:29:59] /home/jenkins/go/pkg/mod/github.com/gogf/gf@v1.16.6/net/ghttp/ghttp_server.go:319 +0x68 fp=0x7f28519a90 sp=0x7f28519a00 pc=0x12e4358
[06:29:59]manta/httpapi.Run()
[06:29:59] /home/jenkins/workspace/ECB2-AS1616D-IR/packshop/source/manta/httpapi/boot.go:58 +0x4b4 fp=0x7f28519f40 sp=0x7f28519a90 pc=0x1ecd464
[06:29:59]main.main()
[06:29:59] /home/jenkins/workspace/ECB2-AS1616D-IR/packshop/source/manta/main.go:177 +0x74 fp=0x7f28519f70 sp=0x7f28519f40 pc=0x1fa66b4
[06:29:59]runtime.main()
[06:29:59] /opt/go/src/runtime/proc.go:250 +0x200 fp=0x7f28519fd0 sp=0x7f28519f70 pc=0xdcc110
[06:29:59]runtime.goexit()
[06:29:59] /opt/go/src/runtime/asm_arm64.s:1172 +0x4 fp=0x7f28519fd0 sp=0x7f28519fd0 pc=0xdff5e4
[06:29:59]

Expected behavior and actual result.

It crashed in the Go Ctrip framework, and the cause of the trigger is currently unknown

Urgent help to check the problem and how to solve/avoid it

THANKS!!

Additional information

No response