Live-share: Debug adapter process has terminated unexpectedly

Created on 15 Nov 2018  路  12Comments  路  Source: MicrosoftDocs/live-share

Issue Type: Bug

Debug adapter process has terminated unexpectedly (Error: Cannot read property 'type' of undefined
{"seq":1,"type":"response","request_seq":1,"command":"initialize","success":true,"body":{"exceptionBreakpointFilters":[{"label":"All Exceptions","filter":"all","default":false},{"label":"Uncaught Exceptions","filter":"uncaught","default":false}],"supportsConfigurationDoneRequest":true,"supportsSetVariable":true,"supportsConditionalBreakpoints":true,"supportsCompletionsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsRestartFrame":true,"supportsExceptionInfoRequest":true,"supportsDelayedStackTraceLoading":true,"supportsValueFormattingOptions":true,"supportsEvaluateForHovers":true,"supportsLoadedSourcesRequest":true,"supportsLogPoints":true,"supportsTerminateRequest":false}}
Error: Cannot read property 'type' of undefined
{"seq":1,"type":"response","request_seq":1,"command":"initialize","success":true,"body":{"exceptionBreakpointFilters":[{"label":"All Exceptions","filter":"all","default":false},{"label":"Uncaught Exceptions","filter":"uncaught","default":false}],"supportsConfigurationDoneRequest":true,"supportsSetVariable":true,"supportsConditionalBreakpoints":true,"supportsCompletionsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsRestartFrame":true,"supportsExceptionInfoRequest":true,"supportsDelayedStackTraceLoading":true,"supportsValueFormattingOptions":true,"supportsEvaluateForHovers":true,"supportsLoadedSourcesRequest":true,"supportsLogPoints":true,"supportsTerminateRequest":false}}
at t.handleData (c:\Users\PJ\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:375:334)
at Socket. (c:\Users\PJ\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:374:761)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20))

Extension version: 0.3.954
VS Code version: Code - Insiders 1.30.0-insider (df8ea54c5397e67b3e47df15a355bd04345c6934, 2018-11-15T06:21:02.187Z)
OS version: Windows_NT x64 10.0.17134


System Info

|Item|Value|
|---|---|
|CPUs|AMD FX(tm)-8150 Eight-Core Processor (8 x 3901)|
|GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
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: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled|
|Memory (System)|31.90GB (20.55GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|


Most helpful comment

We will investigate on our side. FYI, we recently changed the way we host debug session on live share and i presume all this type of errors will go away, but the current version enabled this only for experimental option. We will soon migrate to enable the new mechanism by default

All 12 comments

@pjninnim FYI I'm also having the same problem.

Can you provide more context which language is affected? Did the error happen on the host side? Are you sharing a workspace when the error happen?

@rodrigovaras Trying to just run the debugger with the extension enabled gives the error when debugging a node/javascript. Disable the live share extension and debugger loads correctly. Only started happening from Tuesday, this week with one of the vscode updates. If was all perfect before that.

My launch code is below if it helps:

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Server",
      "program": "${workspaceFolder}/server",
      "cwd": "${workspaceFolder}",
      "env": {
        "NODE_ENV": "development",
        "PJWD_DEV_ENV": "splitServer"
      },
      "skipFiles": [
        "node_modules/**/*.js"
      ]
    },
    {
      "type": "node",
      "request": "launch",
      "name": "Client",
      "program": "${workspaceFolder}/server",
      "cwd": "${workspaceFolder}",
      "env": {
        "NODE_ENV": "development",
        "PJWD_DEV_ENV": "splitClient"
      },
      "sourceMapPathOverrides": {
        "webpack:///src/*": "${workspaceRoot}/src/*"
      },
      "sourceMaps": true,
      "skipFiles": [
        "node_modules/**/*.js"
      ],
      "outFiles": [
        "${workspaceRoot}/dist/*.js"
      ]
    }
  ],
  "compounds": [
    {
      "name": "Server/Client",
      "configurations": ["Server", "Client"]
    }
  ]
}

We will investigate on our side. FYI, we recently changed the way we host debug session on live share and i presume all this type of errors will go away, but the current version enabled this only for experimental option. We will soon migrate to enable the new mechanism by default

@pjninnim can you see if setting liveshare.features = experimental fixes the issue for you?

@srivatsn I just tried all 3 options... default, stable and experimental (what I has set by default) and the error occurs when using all 3 choices.

Thanks. That's good to know. We'll look into this. /cc @jramsay

Thanks for the info @pjninnim! I've tested it out and can also repro the issue (on Insiders only - Stable is fine) when liveshare.features is set to experimental.

Can you try setting your user options explicitly to "stable" again? After you do this you'll have to close and reopen VS Code Insiders for this setting to be applied. Can you let me know if this resolves the issue?

image

@jramsay Thanks. Yes setting it to 'stable' then closing and reopening did resolve the issue.

Glad to hear! If you update VS Code Insiders you should be able to switch back to VS Live Share _experimental_. The issue has been resolved in their latest update.

@jramsay Thanks. I can confirm the latest update has resolved the issue.

@jramsay As I said before it has resolved the issue but I've noticed it has only solved it for initial start / stop. If you start up the debugger, then restart it you receive this:

image

Was this page helpful?
0 / 5 - 0 ratings