node.js - Visual Studio 2022 Unknown thread id '0' - Stack Overflow

admin管理员组

文章数量:1317906

I'm developing a nodejs web application.

I haven't had visual studio opened in some months, and I've updated from windows 10 to 11 since then, so I'm unsure at what point this problem started to occur.

Whenever I start debugging in Visual Studio 2022 I'm getting this error if I close down the console window while visual studio is on a break point or on an error.

When I click OK it takes a few seconds and I will get this error. If I click Stop Now or just wait it will take a little while (about 30 seconds) and the program will exit debugging

I have tried reinstalling Visual Studio.

I have tried deleting the .vs file

I have tried using a blank project.

Searching any of the errors on google doesn't give me anything. At All.

The error persists and its incredible annoying to have to wait that long if I fet to continue the debugging before closing down the console

** UPDATE **

I tried updating nodejs to the most recent version (23.6.1) without any luck.

I also tried running other types of projects (C# console app, Blazor web app) to check if I'm running into the same error, which I'm not. They are working as expected

** UPDATE 2 **

I posted the error on the Visual Studio forum and they guided me towards the preview edition which does fix the error. So for now you can use that to get around the problem, and in the future this should have been fixed

I'm developing a nodejs web application.

I haven't had visual studio opened in some months, and I've updated from windows 10 to 11 since then, so I'm unsure at what point this problem started to occur.

Whenever I start debugging in Visual Studio 2022 I'm getting this error if I close down the console window while visual studio is on a break point or on an error.

When I click OK it takes a few seconds and I will get this error. If I click Stop Now or just wait it will take a little while (about 30 seconds) and the program will exit debugging

I have tried reinstalling Visual Studio.

I have tried deleting the .vs file

I have tried using a blank project.

Searching any of the errors on google doesn't give me anything. At All.

The error persists and its incredible annoying to have to wait that long if I fet to continue the debugging before closing down the console

** UPDATE **

I tried updating nodejs to the most recent version (23.6.1) without any luck.

I also tried running other types of projects (C# console app, Blazor web app) to check if I'm running into the same error, which I'm not. They are working as expected

** UPDATE 2 **

I posted the error on the Visual Studio forum and they guided me towards the preview edition which does fix the error. So for now you can use that to get around the problem, and in the future this should have been fixed

• node.js
• debugging
• visual-studio-2022

Share Improve this question Follow edited Feb 2 at 15:32 Nihilum asked Jan 22 at 17:00 NihilumNihilum 5599 bronze badges 4

• What do you mean "f I close down the command line window"? Could you please provide a screenshot/detailed information or A minimal, reproducible example to help me better understand your scenario? – Dou Xu-MSFT Commented Jan 23 at 5:46
• I mean the nodejs terminal that opens when you start a nodejs project. All I have to do is to create a blank nodejs project, write any code that gives a runtime error or place a debug point and run it with debugging enabled, then close the terminal while visual studio is paused due to the debug point/error – Nihilum Commented Jan 23 at 13:46
• It only happens if visual studio is paused. If I press F5 until I've passed all debug points/errors and close the terminal, it closes as excpeted – Nihilum Commented Jan 23 at 13:52
• I'm also encountering this error since updating VS a few versions ago. I do not use node.js. Stopping an asp service often does this. – Dunge Commented Jan 30 at 20:27

Add a comment  | 

2 Answers 2

Sorted by: Reset to default 2

I followed you steps and can reproduce this issue in VS2022(17.12.4). I also noticed an error message "The thread 'app.js [11036]' (0) has exited with code 0 (0x0)." in output window. Looks like it's a product issue.

I would suggest you to report this issue at Visual Studio Forum. That will allow you to directly interact with the appropriate product group, and make it more convenient for the product group to collect and investigate your issue.

Check Node.js Debugging Settings

Ensure you have the correct debugging configuration in your project settings: Open your project in Visual Studio. Go to Project Properties > Debug.

Verify that the Node.js executable path is correctly set. It should point to the Node.js runtime installed on your system. Ensure that the "Enable Node.js debugging" option is selected.

本文标签： nodejsVisual Studio 2022 Unknown thread id 39039Stack Overflow