runtime: recived SIGSEGV in runtime.mapiternext #29496
Comments
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 |
Empirically that crash doesn't make sense because we already deferenced Line 789 in f865b5f unless perhaps garbage collection reaped |
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 |
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. |
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
A local map var, no concurrency. code like this:

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:

The text was updated successfully, but these errors were encountered: