-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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/go: 1.15.5 crashes on compiling workspace on darwin/amd64 with goroutine stack exceeds 1000000000-byte limit #43279
Comments
There are multiple related issues, all outdated: https://github.com/golang/go/search?q=goroutine+stack+exceeds+1000000000-byte+limit&type=issues |
These are not related. "goroutine stack exceeds 1000000000-byte limit" is just the error the Go runtime prints on stack overflow. In this case, it seems we're stuck in a loop that goes
|
Still haven't seen this repeated and I have been on 1.15.5 since it was released. |
This recursion loop indicates that the @andig Could you tell us more about what you were doing when this happened? Just the stack may not be enough to reproduce this and track the problem down unfortunately. |
I was refactoring code, i.e. moving stuff between packages and updating references all in VS Code. It‘s the first time I‘ve ever seen this and never since. Given there‘s apparently too little content to do anything I‘d suggest to close and I‘ll keep an eye open. |
@andig I'll close this then. Please comment though if you see it again. |
This could be due to the same underlying bug as #25830. The file and line numbers are different, but the pattern of offsets looks like it could plausibly be the same cycle of calls. |
Duplicate of #25830 |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
only happened once sofar
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Compile vscode workspace
What did you expect to see?
no crash
What did you see instead?
The text was updated successfully, but these errors were encountered: