-
Notifications
You must be signed in to change notification settings - Fork 348
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes/No
Yes
- VS Code Version: 1.92.2
- OS Version: MacOS 14.6.1 (23G93)
Steps to Reproduce:
I'm using node v18.20.3
- Create an
app.jsfile with the contentsetInterval(()=>{console.log('alive')}, 1000) - Start 2 or more node processes with
node --inspect=:9223 app.jsand --inspect=:9224 app.js`, etc. - Click on Run & debug and select "Attach by process ID"
{ "name": "Attach by Process ID", "processId": "${command:PickProcess}", "request": "attach", "skipFiles": ["<node_internals>/**"], "type": "node" }, - On the "PickProcess" dropdown you should see at least the 2 processes started on step 1)
- Pick one of them

- Regardless the one wich is picked, the debugger won't be attached (timeout)
The default debug port 9229 seems to be used by vscode for both procesess, wich is not the specified by any of the running node processes.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded