-
Notifications
You must be signed in to change notification settings - Fork 18k
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
x/tools/gopls: automated issue report (crash) - many different random crash patterns #50433
Comments
This is the all log.txt I did nothing, but only read the code and jump to the function definition or something else, the error popup up several times. |
Happy new year, @Airren! Did you set any any User is using multi-root setup that opens folders under the GOPATH/src directory
Multiple different crash patterns are found in this log. It's so badly broken that I suspect memory corruption or race...
Has many cgo-related errors, and missing dependency errors, and messages like "falling back to safe trimming due to type errors".
Transferring to the gopls issue tracker. And another problem is the crash stack dump is so large that VSCode's automated issue report that checks only the last part of the log couldn't capture the panic signature. (That will be tracked separately in vscode-go issue tracker) |
That "unbalanced scopes" error is particularly concerning for me, as it is possibly related to some parser refactoring I did for Go 1.17. But I've never seen it reported before, and I'm really surprised for it to be reported for the first time so long after go 1.17 came out. It could be memory corruption, but I don't understand how it would manifest in this way. @Airren is this reproducible on your end? |
I stared at the "unbalanced scopes" issue in |
I think without more information here we can't spend more time tracking this down. It seems to be a very broken machine (though in surprising ways). If this is reproducible we can perhaps understand it. |
Closing. Please reopen if you are able to reproduce. |
gopls version: v0.7.4
gopls flags:
update flags: proxy
extension version: 0.30.0
go version: 1.17.5
environment: Visual Studio Code linux
initialization error: undefined
issue timestamp: Tue, 21 Dec 2021 01:44:03 GMT
restart history:
Tue, 21 Dec 2021 01:43:32 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.
Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.
Failed to auto-collect gopls trace: no gopls log.
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>
The text was updated successfully, but these errors were encountered: