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

runtime: recived SIGSEGV in runtime.mapiternext #29496

Closed
zct opened this issue Jan 2, 2019 · 4 comments
Closed

runtime: recived SIGSEGV in runtime.mapiternext #29496

zct opened this issue Jan 2, 2019 · 4 comments

Comments

@zct
Copy link

@zct zct commented Jan 2, 2019

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

$ go version
1.9

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

go env Output
$ go env

What did you do?

A local map var, no concurrency. code like this:
image

panic in line 17. It seems happened only once in my server, I can't Find out why

What did you see instead?

panic call stack trace:
image

@odeke-em
Copy link
Member

@odeke-em odeke-em commented Jan 2, 2019

Thank you for filing this issue @zct and welcome to the Go project!

How often can this problem be reproduced? Would it be possible for you to also try Go1.11 or the Go1.12beta*?

I'll kindly page some experts @randall77 @josharian @ianlancetaylor

@odeke-em
Copy link
Member

@odeke-em odeke-em commented Jan 2, 2019

Empirically that crash doesn't make sense because we already deferenced it *hiter before we hit that line on which it crashed

if bucket == it.startBucket && it.wrapped {

unless perhaps garbage collection reaped it the pointer to the map iterator. For that I'll also page @aclements @RLH

@zct
Copy link
Author

@zct zct commented Jan 3, 2019

Thank you for filing this issue @zct and welcome to the Go project!

How often can this problem be reproduced? Would it be possible for you to also try Go1.11 or the Go1.12beta*?

I'll kindly page some experts @randall77 @josharian @ianlancetaylor

thank you for your kindly reply, It seems can't reproduce. If it happened again, I'll post full stack trace log. My server was stable running for half an year, this is first panic I received. For me, it's looks like a strange behavior in golang

@agnivade
Copy link
Contributor

@agnivade agnivade commented Jun 19, 2019

Hello @zct - I would request you to try with the latest 1.12 release and report back if you still see the crash. And just to be sure there are no races, please ensure to run with the -race flag.

@zct zct closed this Jun 19, 2019
@golang golang locked and limited conversation to collaborators Jun 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

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