-
Notifications
You must be signed in to change notification settings - Fork 767
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
VSCode crash by Go #469
Comments
@NhokCrazy199 Thanks for the bug report. It looks like the original exception was from the go-outliner extension (766b.go-outliner). But the exception from other extension started to affect our extension since Go 0.16.0 release. The code that threw an error is originated from goDlvDebug.ts:
This is installing a process-wide uncaught exception handler. It was packed in The dlv dap debug adapter is still in early stages, so I think it's better not to inline. |
Hi, @hyangah. Is there any solution? Any way I can help? Is more info needed? Let me know since this same error is happening to me. I guess this information could be relevant:
|
Change https://golang.org/cl/246777 mentions this issue: |
@ivanovishado thanks! In the mean time, roll back to 0.15.2. Extensions view -> Select "Go" extension -> Click the gear icon -> Install Another Version... -> Choose 0.15.2. |
Thanks, @hyangah! |
This is not yet released. Since this is a major bug, I will keep this open until it's released and verified. |
Change https://golang.org/cl/246959 mentions this issue: |
…onfig Eventually we want to inline the debug adapter, but until it gets more stable and becomes the default adapter, let's launch it as a separate process to isolate failures. This is handled by the definition in package.json. In order to avoid accidental installation of the process-wide uncaughtException handler when we switch back to the inline mode, move the handler out of goDlvDebug.ts. Also, fixes the default configuration provider for delve dap debug adapter. It should use 'godlvdap' as the type. Fixes #469 Updates #23 Change-Id: I4df2fff51c703995fd557fe5595a367d7048bd7b Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/246777 Reviewed-by: Polina Sokolova <polina@google.com> (cherry picked from commit f9c0454) Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/246959 Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: kokoro <noreply+kokoro@google.com> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
RC.1 is out. https://github.com/golang/vscode-go/releases/tag/v0.16.1-rc.1 @NhokCrazy199 @ivanovishado @zhanswift Can you check if the RC1 addresses this issue? |
@hyangah, I installed it and restarted Code several times. No issues so far. 👍 |
Thanks all for verifying the fix. 0.16.1 is released. |
Issue Type: Bug
c:\Users\PhamK.vscode\extensions\golang.go-0.16.0\dist\goMain.js:26315
throw err;
^
SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at c:\Users\PhamK.vscode\extensions\766b.go-outliner-0.1.20\out\app.js:187:45
at ChildProcess.exithandler (child_process.js:315:5)
at ChildProcess.emit (events.js:203:13)
at ChildProcess.EventEmitter.emit (domain.js:476:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Extension version: 0.16.0
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z)
OS version: Windows_NT x64 10.0.19041
The text was updated successfully, but these errors were encountered: