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: fatal error: throwOnGCWork (and general builder instability) #29124

Open
eliasnaur opened this Issue Dec 6, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@ianlancetaylor

This comment has been minimized.

Contributor

ianlancetaylor commented Dec 6, 2018

@aclements

This comment has been minimized.

Member

aclements commented Dec 6, 2018

linux/amd64: https://build.golang.org/log/2ce33c8fa9981d37f3d5a81e384285c0be6df37a
android/arm: https://build.golang.org/log/34a763d60d9908f39856dd7380948081bef8fff9

Dup of #27993. (Definitely a release-blocker. I'm actively working on this one.)

https://build.golang.org/log/8b9d9127e958601e4a0a3aa71243463d814bd92e
https://build.golang.org/log/8aa5d8614243f1aea5354ba3598e66143de3249c
https://build.golang.org/log/80435e9f9573e9eec360dcb0a69772ca4ccf991a
https://build.golang.org/log/24e04fb21e1383cd002c3a575398f38cf15c7532

Dup of #25519. Only affects debug call injection, so not high-priority. This isn't technically Android-specific, though it seems to happen a lot there, so maybe we should just disable that test on Android.

https://build.golang.org/log/994e945a2a0f4e4ac2efdbabf9c7fedcf402553e

Stuck doing a syscall.Open?

@eliasnaur

This comment has been minimized.

Contributor

eliasnaur commented Dec 6, 2018

https://build.golang.org/log/994e945a2a0f4e4ac2efdbabf9c7fedcf402553e

Stuck doing a syscall.Open?

I believe the vet process used ~100% cpu when I sent it SIGQUIT. So an infinite loop somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment