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: sigpanic in scanframeworker #28353

Open
tbg opened this issue Oct 24, 2018 · 2 comments
Open

runtime: sigpanic in scanframeworker #28353

tbg opened this issue Oct 24, 2018 · 2 comments
Milestone

Comments

@tbg
Copy link

@tbg tbg commented Oct 24, 2018

A crash with the following stack trace on go1.10.3 was reported anonymously from a CockroachDB server (8 CPUs):

*log.safeError: stopper.go:182: runtime.errorString: runtime error: invalid memory address or nil pointer dereference
  File "runtime/asm_amd64.s", line 573, in call32
  File "runtime/panic.go", line 502, in gopanic
  File "runtime/panic.go", line 63, in panicmem
  File "runtime/signal_unix.go", line 388, in sigpanic
  File "runtime/mgcmark.go", line 827, in scanframeworker

My best reading of this is that scanframeworker code tried to log and instead hit an NPE (not sure where though, frame shouldn't be nil as it's already dereferenced earlier in the code):

print("runtime: frame ", funcname(f), " untyped locals ", hex(frame.varp-size), "+", hex(size), "\n")

If this hadn't NPEd, the stack trace would've been something like #17499.

Unfortunately, due to the nature of the report, I can neither reproduce this nor do I have more information about the environment in which this happened.

@bcmills

This comment has been minimized.

Copy link
Member

@bcmills bcmills commented Oct 24, 2018

@bcmills bcmills changed the title runtime: NPE before throw("missing stackmap") in scanframeworker runtime: sigpanic in scanframeworker Oct 24, 2018
@bcmills bcmills added this to the Go1.10.5 milestone Oct 24, 2018
@tbg

This comment has been minimized.

Copy link
Author

@tbg tbg commented Oct 24, 2018

I should add that this happened on linux-amd64.

@dmitshur dmitshur modified the milestones: Go1.10.5, Go1.10.6 Nov 1, 2018
@dmitshur dmitshur modified the milestones: Go1.10.6, Go1.10.7 Dec 13, 2018
@FiloSottile FiloSottile modified the milestones: Go1.10.7, Go1.12 Dec 14, 2018
@andybons andybons modified the milestones: Go1.12, Go1.13 Feb 12, 2019
@andybons andybons modified the milestones: Go1.13, Go1.14 Jul 8, 2019
@rsc rsc modified the milestones: Go1.14, Backlog Oct 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

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