Yep - this is my bad. We added a feature to suggest filing an issue in the latest version of the VS Code Go plugin when gopls crashes. I guess I didn't realize that it crashed this much, and the gopls bug command we're using isn't clear enough that the user needs to write something here. I will try to merge https://go-review.googlesource.com/c/tools/+/240503 for the gopls/v0.4.2 release tomorrow, which will hopefully address this. I also filed golang/vscode-go#276 so that we remember to attach the stack trace to these crashes.