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

cmd/compile: infinite loop in cmd/compile/internal/gc.compileFunctions (darwin/amd64) #29418

Closed
eliasnaur opened this issue Dec 25, 2018 · 1 comment

Comments

@eliasnaur
Copy link
Contributor

@eliasnaur eliasnaur commented Dec 25, 2018

From the Android builder. I had to kill the compile process with SIGQUIT:

https://farmer.golang.org/temporarylogs?name=android-arm64-wiko-fever&rev=b32ee0a3c004d4ef79d92bd63200008456da50f3&st=0xc447882b00

Note that the hung process was before running tests, running on the host (darwin/amd64 mac mini).

The infinite loop reminds me of a similar case reported in #29124:

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

That was for the vet binary but the symptoms were the same: a 100% CPU hung process. Same builder, but a host binary.

@eliasnaur eliasnaur changed the title cmd/compile: infinite loop in cmd/compile/internal/gc.compileFunctions darwin/amd64 cmd/compile: infinite loop in cmd/compile/internal/gc.compileFunctions (darwin/amd64) Dec 25, 2018
@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Dec 26, 2018

Closing as dup of #29385.

@golang golang locked and limited conversation to collaborators Dec 26, 2019
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
3 participants
You can’t perform that action at this time.