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: SIGSEGV in readgstatus via gcAssistAlloc #48845

Closed
bcmills opened this issue Oct 7, 2021 · 1 comment
Closed

runtime: SIGSEGV in readgstatus via gcAssistAlloc #48845

bcmills opened this issue Oct 7, 2021 · 1 comment
Labels
NeedsInvestigation
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Oct 7, 2021

greplogs --dashboard -md -l -e '(?m)unexpected signal during runtime execution\n(.*\n)*runtime stack:\n(?:.+\n\t.+\n)*runtime\.readgstatus.*\n\t.+\n(?:.+\n\t.+\n)*runtime\.gcAssistAlloc'

2021-10-07T14:01:52-ecb2f23/android-386-emu
2021-10-06T19:59:27-62292e8-17c513e/android-amd64-emu
2021-10-05T20:53:02-d4b1ae0-695a59b/android-amd64-emu
2021-03-08T20:41:06-a08adda/linux-mips64le-rtrk

This looks to me like it may be closely related to #43824 (CC @prattmic @mknyszek)

@bcmills bcmills added the NeedsInvestigation label Oct 7, 2021
@bcmills bcmills added this to the Backlog milestone Oct 7, 2021
@gopherbot
Copy link

@gopherbot gopherbot commented Dec 1, 2021

Change https://golang.org/cl/368134 mentions this issue: runtime: fix racy allgs access on weak memory architectures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation
Projects
None yet
Development

No branches or pull requests

2 participants