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

'Cannot read property 'toString' of null.' when starting debugger for second+ time #43490

Closed
richardfuca opened this issue Feb 12, 2018 · 1 comment
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

@richardfuca
Copy link

richardfuca commented Feb 12, 2018

Issue Type

Bug

Description

Steps to Reproduce:

  1. Have project open, with "console" in debugger launch configuration set to "integratedTerminal"

  2. Start debugging the program (F5), then quit the application (ex. by using Ctrl-C). Keep the Node Debug Console open.

  3. Try debugging the program again (F5)

OR

  1. Start debugging the program (F5), then click on the Restart button

Expected:
Debugger and program should load like it does in step 2

Actual:
This error occurs:

TypeError: Cannot read property 'toString' of null
at Function.e.isBusy (terminalSupport.ts:56)
at Function.e.runInTerminal (terminalSupport.ts:38)
at _.dispatchRequest (rawDebugSession.ts:393)
at _.e.dispatch (v8Protocol.ts:148)
at _.e.handleData (v8Protocol.ts:104)
at Socket. (v8Protocol.ts:41)
at emitOne (events.js:96)
at Socket.emit (events.js:191)
at readableAddChunk (_stream_readable.js:178)
at Socket.Readable.push (_stream_readable.js:136)

VS Code Info

VS Code version: Code 1.20.0 (c63189d, 2018-02-07T17:09:39.780Z)
OS version: Windows_NT x64 6.1.7601

System Info
Item Value
CPUs AMD Phenom(tm) II X6 1090T Processor (6 x 3199)
Memory (System) 16.00GB (10.01GB free)
Process Argv C:\Program Files\Microsoft VS Code\Code.exe
Screen Reader no
VM 0%
Reproduces without extensions
@roblourens roblourens assigned isidorn and unassigned roblourens Feb 13, 2018
@isidorn isidorn assigned weinand and unassigned isidorn Feb 13, 2018
@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Feb 13, 2018
@weinand
Copy link
Contributor

weinand commented Feb 13, 2018

I cannot reproduce this problem.
Did you configure the integrated terminal in any way, e.g. by setting a special shell via the "terminal.integrated.shell.windows" setting?

@weinand weinand added this to the February 2018 milestone Feb 13, 2018
@mjbvz mjbvz added the verified Verification succeeded label Mar 1, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 30, 2018
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

5 participants