-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
Debugger doesn't exit after program run #5709
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
What node version are you using? |
What command are you running to start it? Can you please post the example to something like gist or another pasting service? (Also please try to make a test-case that does not require npm modules to reproduce.) |
I have lost my VM over the weekend so I can't tell. But I'm sure it was Node 4. |
For details on how I started the Node debugger, please refer to the issue I cross-referenced above: |
Unfortunately this is not quite enough information to go off of. I know it may be difficult to do so, but we'll need a reproduceable test case that demonstrates the issue before we can adequately diagnose the problem. |
Of course, I apprehend. Yesterday I was able to setup a new VM with latest versions of all my development software. I'll create a test case over the weekend and keep you updated. |
I'm going to investigate this week |
Great. Thanks! |
I'm going to close this as a duplicate of #1788 I'll be continuing my investigation in that thread |
When debugging the following simple project (only a
gulpfile.js
) in VS Code, the debugger doesn't exit after the last line of code has been executed:Gulp4ParallelTest.zip
The VS Code team suggests that this is a problem in the Node runtime.
I feel it's quite confusing not to safely know whether all threads/processes in a program have finished or not when debugging.
The text was updated successfully, but these errors were encountered: