Debug process didn't close after finish debugging

Question

Debug process didn't close after finish debugging

kiddkai opened this issue 10 years ago · 35 comments

kiddkai commented 10 years ago

In both io.js and node.js >= 0.12 have this issue.

OS:

osx & ubuntu 14

Reproduce steps:

Create a file:

a.js

console.log('debug');

run node debug a.js
press c to continue

Then the stdout should have:

> debug
> program terminated

But currently, it only have

> debug

When I try to press c to continue and make the process close, but it just stuck there waiting for v8 response.

It happen when I write my own debugger. It seems that the debug server should knows that the process is terminated, but it didn't.

Answer 1 · 2015-06-17T07:30:43.000Z

cross-ref: nodejs/node-v0.x-archive#25358
i'll mark as confirmed-bug because the joyent folks seem to have also

Answer 2 · 2015-07-13T01:01:21.000Z

Trying it on mac, latest atom, Node 0.12.4, and it doesn't seem to work. F5 just says "finish debugging :) "

Answer 3 · 2015-07-13T06:40:10.000Z

Hey @pitosalas , it seems that your configuration is not correct. Which can not find the node.js binary? Is there any error popup shows up? Anyway, please move the node-debugger conversation to https://github.com/kiddkai/atom-node-debugger.

Here is the issues for io.js.

Answer 4 · 2015-09-30T14:21:52.000Z

Hi, i don't know how...and why...but all shortcuts are disabled.
I don't see any "Enable" checkbox in settings page, what can you do to fix it ?

OS: Windows 7 64bit

Ty

Answer 5 · 2015-10-29T15:00:40.000Z

#2778 got reverted in 9b02442 so this issue is still relevant.

Answer 6 · 2016-01-08T22:01:40.000Z

This is frustrating me too. I end up restarting my terminal (iTerm2 on this machine) to get out and start again...

Answer 7 · 2016-02-03T01:05:27.000Z

OS: OS X EI Capitian
my Node Path: "/Users/liuhongyu/.nvm/versions/node/v4.0.0/bin/node"
error: node executable could not be found

Answer 8 · 2016-02-29T12:38:26.000Z

All shortcuts are disabled.I am using Windows 7 64 bit system.
Can someone help me out.

Answer 9 · 2016-03-09T03:28:43.000Z

It's possible that this was fixed recently in v5 and master. Can anyone confirm?

Answer 10 · 2016-04-02T06:41:06.000Z

Nope, still an issue unfortunately. /cc @thealphanerd

Answer 11 · 2016-04-02T09:02:32.000Z

assigned to myself... will dig in next week

Answer 12 · 2016-04-05T00:14:38.000Z

I can confirm that this bug is present in v4, v5, and v0.12. v0.10 appears to work as expected (assuming the exepcted behavior is that the debugger informs you of the program terminating

Answer 13 · 2016-06-27T14:45:36.000Z

i have confirmed this problem from node 4.4.2 to 6.2.2.

I used "node debug a.js" to test debugger.

This works in old version.

This problem affect other product such as WebStorm.

If this is by design, then should let WebStorm fix it.

Answer 14 · 2016-09-27T17:38:56.000Z

Any news about this? I'm still affected using Visual Studio Code and Node 6.5.0

Answer 15 · 2016-10-24T09:05:57.000Z

I'm also still affected using Visual Studio Code 1.6.1 and Node 6.9.1.

Answer 16 · 2016-11-16T05:16:05.000Z

I am having the same experience. Any ideas regarding this development? Node 7.1.0 and VSCode 1.7.1

Answer 17 · 2016-11-24T14:27:47.000Z

For those on Linux (esp using VS code) who want a really hacky way to terminate the debugger on process exit, here you go...

process.on('exit', (code) => {
    // this force terminates the debugger by attaching to the debugger socket via it's FD and destroying it!
    try {
        new require('net').Socket({
            fd: parseInt(
                require('child_process').spawnSync('lsof', ['-np', process.pid], {encoding:'utf8'})
                    .stdout.match(/^.+?\sTCP\s+127.0.0.1:\d+->127.0.0.1:\d+\s+\(ESTABLISHED\)/m)[0].split(/\s+/)[3]
                , 10)
        }).destroy();
    } catch(e) {}
});

Answer 18 · 2017-05-30T04:12:45.000Z

Closing this. If this is still an issue that needs to be fixed, we can reopen.

Answer 19 · 2017-05-31T00:34:00.000Z

@jasnell, on what basis did you close this bug?

It seems to be a long-standing Node bug that keeps popping up (usually other front-end debugging tools are inappropriately blamed). Why can't it be acknowledged and then fixed?

Answer 20 · 2017-05-31T00:37:26.000Z

The old debugger has been deprecated and removed as of 8.0.0. While this issue may be relevant still in older versions, and while I'd really like to see these older issues addressed, the likelihood that someone with enough domain expertise to resolve the issue is going to pick it issue up and fix it in 6.x or 4.x is fairly low, unfortunately. We can certainly reopen the issue but we would need someone to move it forward.

Answer 21 · 2017-05-31T00:45:54.000Z

@jasnell, so this is fixed in the new debugger?

I am using Visual Studio Code. Do you have any pointers for using the new debugger with it?

Just install node 8.0?

Answer 22 · 2017-05-31T09:42:48.000Z

@mattflix It's covered in their documentation here: https://code.visualstudio.com/docs/nodejs/nodejs-debugging

Answer 23 · 2017-05-31T12:43:25.000Z

I see no problem closing the issue.

Overall I am very happy with the debugging progress in Node. Using the --inspect flag and chrome devtools is an immense boost in productivity. Thanks @jasnell @bnoordhuis and all. ✨🙏✨

Answer 24 · 2017-06-22T08:56:20.000Z

I'm still having this issue by using VS Code 1.13.1 / Node 8.1.1. If I run a gulp task, it won't get finished until I stop the debugger.

Answer 25 · 2017-06-22T16:33:06.000Z

I confirm the same problem with code 1.13.1 and node v8.1.2

Answer 26 · 2017-06-26T15:42:11.000Z

Still a problem in node v8.1.2. Please re-open. @jasnell

Answer 27 · 2017-06-26T18:12:15.000Z

What is? Please be specific.

Answer 28 · 2017-06-26T19:08:30.000Z

Actual behavior
debug session does not stop when node script has finished running

Expected behavior
when a node script has finished running, the debug session should end

Steps to reproduce

Open an empty folder in VSCode
Add a default launch debug configuration (Debug->Add Configurations...)
Create a .js file with contents console.log('test');
Launch the debugger
Observe that the debug toolbar stays active and indicates that the script is executing after 'test' has been written to the console

OS: Ubuntu 17.10 & MacOS Sierra
Node: v8.1.2
Editor: Visual Studio Code 1.13.1

@bnoordhuis

Answer 29 · 2017-06-27T19:34:34.000Z

@millermatt Thanks. Is there reason to assume it's a node.js issue? It sounds like a tooling issue in VS Code.

Answer 30 · 2017-06-27T20:29:52.000Z

microsoft/vscode#5831 (comment)

The above issue in the VS Code repo led me to this node.js issue. I can't say for certain whether the problem is with VS Code or node.js. Based on the conversations in both issues it seems more likely that is a node.js problem.

@bnoordhuis

Answer 31 · 2017-06-28T08:50:20.000Z

@millermatt Right, but that was with the old debugger, which has been removed. The inspector (the new debugger) is completely different so it's unlikely to be the same issue.

I'd take this up with the VS Code people first. If it does turn out to be a node.js issue, file a new issue and I'll take a look.

Answer 32 · 2017-06-29T02:31:57.000Z

@bnoordhuis Good call - looks like they have a fix for the next release. microsoft/vscode-node-debug2#11

Answer 33 · 2017-07-20T06:55:31.000Z

For anyone googling, couldn't make the process exit with process.exit() when debugger was attached, but process.kill(process.pid) worked

Answer 34 · 2017-10-12T08:43:27.000Z

This still happens with node 8.7.0 under Webstorm debugging. Seems to be related to node rather than the IDE.

Answer 35 · 2017-10-16T14:59:56.000Z

@georgeionita can you give detailed steps to reproduce?