Javascript debugger not working

[AlCalzone]

Does this issue occur when all extensions are disabled?: Yes, but this needs the JS debugger

• VS Code Version: 1.74.3
• OS Version: Ubuntu 22.04.1 LTS

Steps to Reproduce:

// file: test.js
debugger;
console.log("after debugger"); // put breakpoint here

1. execute node test.js in Javascript debug console
2. notice that "after debugger" is logged, debugger does not attach

alternatively add this launch config:

		{
			"name": "Test Program",
			"program": "${workspaceFolder}/test.js",
			"request": "launch",
			"skipFiles": ["<node_internals>/**"],
			"type": "node"
		},

1. run it
2. debugger does not launch, program exits at the end

[AlCalzone]

I'm starting to think this may be system or configuration related. I went all the way back to 1.66.2 (and I've definitely debugged this way last summer), yet the debugger does not attach.

[AlCalzone]

Even with auto-attach set to "always", nothing happens here:

[AlCalzone]

Tested on a different machine with Windows 10 instead of Ubuntu, here it works.
Also tested inside a devcontainer on the Ubuntu machine, here it works too.
So this must be something env-specific, but I have no idea what.

[connor4312]

What is the result of echo $NODE_OPTIONS in the JavaScript Debug Terminal?

[AlCalzone]

Devcontainer (working):

--require /vscode/vscode-server/bin/linux-x64/97dec172d3256f8ca4bfb2143f3f76b503ca0534/extensions/ms-vscode.js-debug/src/bootloader.bundle.js --inspect-publish-uid=http

Ubuntu (not working):

--require /usr/share/code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js --inspect-publish-uid=http

Windows (with git bash, working):

--require "c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js" --inspect-publish-uid=http

[connor4312]

What version of Node.js are you using in the "not working" sample?

[AlCalzone]

16.19.0

The devcontainer is on 18.13.0 and the Windows machine on 12.x or 14.x

[connor4312]

Do you have any capabilities set on your Node binary? You may be hitting nodejs/node#37588

[AlCalzone]

sudo getcap $(which node)
/usr/bin/node cap_net_bind_service,cap_net_admin,cap_net_raw=eip

that might be it

[AlCalzone]

That was it! Thanks for the pointers, removing the capabilities fixed it.