-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: pointer 0xe9f4d95300 to unused region of span span.base()=0xc311776000 span. limit=0xc311778000 span.state=1 #51552
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
This looks like memory corruption. Have you tried running your program under the race detector? See https://blog.golang.org/race-detector . |
No, I'll try it later ,thanks |
Using atomic to write shared variables alone has been around for a long time and didn't crash before.================== Previous write at 0x00c01be2fde8 by goroutine 41: Goroutine 38 (running) created at: Goroutine 41 (running) created at: Also, every time it crashes, it is found that there is a call at runtime/mwbbuf.go. The code for report.go 123 is as follows:
220308.175025|runtime: pointer 0xe9f4d95300 to unused region of span span.base()=0xc311776000 span.limit=0xc311778000 span.state=1 |
Sorry to report that if your program has a data race, the results are undefined. I’m going to close this issue for the moment, please feel, once you’ve addressed the data races, to comment if your are still experiencing crashes. |
What version of Go are you using (
go version
)?1.16.15
Does this issue reproduce with the latest release?
Yes, 1.17.6, 1.17.7 and 1.17.8 reproduce
What operating system and processor architecture are you using (
go env
)?go env
Outputcentos8 linux ,x86-64
What did you do?
There are a lot of code changes that have been running normally in one production environment, and often crashed and exited in another environment.
What did you expect to see?
What did you see instead?
220308.175025 runtime: pointer 0xe9f4d95300 to unused region of span span.base()=0xc311776000 span. limit=0xc311778000 span.state=1
520308.175025 fatal error: found bad pointer in Go heap ( incorrect use of unsafe or cgo?)
220308.175025
220308.175025 runtime stack:
220308.175025 runtime.throw(0x8ee39b, 0x3e)
220308.175025 /usr/local/go/src/runtime/panic.go:1117+0x72 fp=0x7f7227ffed88 sp=0x7f7227ffed58 pc=0x43b3f2
220308.175025 runtime.badpointer(0x7f6f0ba6bae0, 0xe9f4d95300, 0x0, 0x0)
220308.175025 /usr/local/go/src/runtime/mbitmap.go:351+0x235 fp=0x7f7227ffeddo sp=0x7f7227ffed88 pc=0x418db5
220308.175025 runtime. findobiect(oxe9f4d95300, 0x0, 0x0, 0xd9b9938b00, 0x7f6ff8305d50, 0xb)
220308.175025 /usr/local/go/src/runtime/mbitmap .go: 387 +0x9b fp=0x7f7227ffee08 sp=0x7f7227ffedd0 pc=0x418e7b
220308.175025 runtime.wbbuffFlush1(0xc000043000)
220308.175025 /usr/local/go/src/runtime/mwbbuf.go:260+0xa8 fp=0x7f7227ffee60 sp=0x7f7227ffee08 pc=0x4360e8
220308.175025 runtime.wbBuffFush.func1()
220308.175025 /usr/local/go/src/runtime/mwbbuf.qo:201+0x3afp=0x7f7227ffee78sp=0x7f7227ffee60pc=0x46b69a
220308.175025 runtime.systemstack(0xc01bd82180)
220308.175025 /usr/local/go/src/runtime/asm_amd 64.s:379+0x66 fp=0x7f7227ffee80 sp=0x7f7227ffee78 pc=0x4721c6
220308.175025 runtime.mstart()
220308.175025 /usr/local/go/src/runtime/proc.go:1246 fp=0x7f7227ffee88 sp=0x7f7227ffee80 pc=0x4406c0
220308.175025
The text was updated successfully, but these errors were encountered: