Skip to content
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

node2 debugging step over repeatedly throws errors in console #22855

Closed
Eli-Goldberg opened this issue Mar 19, 2017 · 0 comments
Closed

node2 debugging step over repeatedly throws errors in console #22855

Eli-Goldberg opened this issue Mar 19, 2017 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone

Comments

@Eli-Goldberg
Copy link

  • VSCode Version:
    Version 1.11.0-insider
    Commit 05f19ee
    Date 2017-03-17T08:10:26.163Z
  • OS Version: Ubuntu 16.04
  • Node version: v7.7.1

I'm using this in launch.json:

  "type": "node",
  "protocol: "auto"

Steps to Reproduce:

  1. Just open any project
  2. Press F10 very quickly for 3-7 times

This shows up in console:

Error processing "stackTrace": TypeError: Cannot read property 'callFrames' of null
at NodeDebugAdapter. (/usr/share/code-insiders/resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/chromeDebugAdapter.js:879:55)
at next ()
at /usr/share/code-insiders/resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/chromeDebugAdapter.js:10:65
at __awaiter (/usr/share/code-insiders/resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/chromeDebugAdapter.js:6:12)
at NodeDebugAdapter.stackTrace (/usr/share/code-insiders/resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/chromeDebugAdapter.js:877:16)
at dispatchRequest (/usr/share/code-insiders/resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-chrome-debug-core/out/src/chrome/chromeDebugSession.js:74:82)
at ProtocolServer._handleData (/usr/share/code-insiders/resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-debugadapter/lib/protocol.js:104:38)
at Socket. (/usr/share/code-insiders/resources/app/extensions/ms-vscode.node-debug2/node_modules/vscode-debugadapter/lib/protocol.js:24:60)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)

image

@weinand weinand self-assigned this Mar 19, 2017
@weinand weinand added debug Debug viewlet, configurations, breakpoints, adapter issues bug Issue identified by VS Code Team member as probable bug labels Mar 19, 2017
@weinand weinand assigned roblourens and unassigned weinand Mar 19, 2017
@roblourens roblourens added this to the March 2017 milestone Mar 19, 2017
@weinand weinand added the verified Verification succeeded label Mar 30, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants