Debug adapter process has terminated not at all unexpectedly #53535
Description
Issue Type: Bug
The Node debug adapter crashes at least a dozen times every single day for one of my projects.
In a previous ticket I was told that this is not supposed to happen, which is also the reason why no more information regarding the cause is made available to the user. I still think that's a mistake, but I would happily accept a solution where the adapter is simply not crashing anymore.
I'm currently using Node 8.11.1
VS Code version: Code 1.24.1 (24f6262, 2018-06-13T17:51:32.889Z)
OS version: Windows_NT x64 10.0.17134
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz (12 x 3672) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: enabled video_encode: enabled vpx_decode: enabled webgl: enabled webgl2: enabled |
| Memory (System) | 63.91GB (33.61GB free) |
| Process Argv | C:\Program Files\Microsoft VS Code\Code.exe . |
| Screen Reader | no |
| VM | 0% |
Extensions (8)
| Extension | Author (truncated) | Version |
|---|---|---|
| bracket-pair-colorizer | Coe | 1.0.58 |
| vscode-eslint | dba | 1.4.12 |
| EditorConfig | Edi | 0.12.4 |
| vscode-esformatter | how | 1.6.0 |
| output-colorizer | IBM | 0.1.2 |
| vscode-lebab | mrm | 2.5.0 |
| vscode-puglint | mrm | 2.3.0 |
| debugger-for-chrome | msj | 4.7.0 |
(1 theme extensions excluded)