[Insiders] Debugger kept in invalid state after process exits

[a0viedo]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.57.0-insider
• OS Version: Windows 10

I've tested this with all extensions disabled.

Steps to Reproduce:

1. Start a node process with --inspect-brk that uses worker threads
2. Attach the debugger
3. Send a SIGINT signal to the process to terminate it
   

Even if I click on disconnect nothing happens and the debugger still will be on screen. The only solution I've found is to force a "Reload Window".

I've uploaded a video of the reproduction too.

Code:

setInterval(() => {
    console.log('hi there')
}, 1000);

const { Worker } = require('worker_threads');
new Worker(``, { eval: true });

[weinand]

Does the node process terminate properly if you send a SIGINT signal but have no debugger attached?

[a0viedo]

Yes, I would have to disable Auto Attach but it does exit properly. And sorry I didn't include the code for the repo, I've edited it and added that.

[connor4312]

Thanks for the issue. This is because you're debugging twice using both auto attach and a launch config. The 'target IDs' are set for the worker by Node, so the first debug session steals the target for the second session (since they're attaching to the same worker), causing an error to be thrown. This prevents the second session from initializing (and being able to be torn down).

A workaround is to remove the duplicate session, either:

• Don't use auto attach and only Attach using a launch config
• Use auto attach (with --inspect instead of --inspect-brk) instead of the launch config

[a0viedo]

I see. Even with auto attach disabled there was still one debugger open so I couldn't get it work but after restarting the app it worked as expected. Thanks!

[connor4312]

no problem, it should be fixed on nightly

[rzhao271]

@a0viedo has the issue been resolved for you (without having to use a workaround)?

[a0viedo]

@rzhao271 yes, when I managed to get two debuggers attached I had to restart VS Code and disable auto attach to get it working as expected.