Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

TypeError: Cannot read property 'api' of undefined #72

Closed
sgtoj opened this issue Jan 2, 2017 · 3 comments
Closed

TypeError: Cannot read property 'api' of undefined #72

sgtoj opened this issue Jan 2, 2017 · 3 comments

Comments

@sgtoj
Copy link

sgtoj commented Jan 2, 2017

Version 1.9.0-insider
Commit f2379e882b415e2c503a723776c4431a40d7c1aa
Date 2017-01-02T07:11:43.247Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0

I thought someone else already reported this issue but I wasn't able to locate it at vscode-node-debug2, vscode-chrome-debug, vscode-chrome-debug-core, or vscode repositories. Maybe I overlooked it, though?

Issue:

Step to Reproduce

  • Enter node2 debug mode.
Error processing "evaluate": TypeError: Cannot read property 'api' of undefined
    at ChromeConnection.get api [as api] (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeConnection.js:56:28)
    at NodeDebugAdapter.get chrome [as chrome] (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:40:38)
    at NodeDebugAdapter.globalEvaluate (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:1035:20)
    at NodeDebugAdapter.globalEvaluate (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\out\src\nodeDebugAdapter.js:410:22)
    at NodeDebugAdapter.evaluate (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:957:32)
    at dispatchRequest (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugSession.js:122:68)
    at ProtocolServer._handleData (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-debugadapt[...]
Error processing "evaluate": TypeError: Cannot read property 'api' of undefined
    at ChromeConnection.get api [as api] (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeConnection.js:56:28)
    at NodeDebugAdapter.get chrome [as chrome] (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:40:38)
    at NodeDebugAdapter.globalEvaluate (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:1035:20)
    at NodeDebugAdapter.globalEvaluate (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\out\src\nodeDebugAdapter.js:410:22)
    at NodeDebugAdapter.evaluate (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:957:32)

Troubleshooting

  • Affects only VS Code Insiders
  • Affects Node v6.9.2 and v7.3.0
@roblourens
Copy link
Member

Yeah this was reported in microsoft/vscode#17902 and happens when you launch with a watch. Probably needs to be fixed on vscode's end.

@sgtoj
Copy link
Author

sgtoj commented Jan 3, 2017

@roblourens I believe this issue has been resolved as of today's Insiders release. Seems to be resolved on Windows and Ubuntu.

Version 1.9.0-insider
Commit d384271ffb5655cee1ddf8f93f51cd892ee2cc40
Date 2017-01-03T07:03:14.182Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0

@roblourens
Copy link
Member

Great!

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants