You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
When running the project linked above using Debug NPM script, the first call to execSync doesn't seem to clean up properly and the second call hangs and is unable to be debugged. This only happens when the script is run from within VS Code. Running the script from the command prompt completes correctly.
Steps to reproduce:
Run npm i to install dependencies
From a command prompt, run npm run run. The script will complete correctly.
Open the project in VS Code.
Open the command pallette, and run Debug: Debug NPM script.
Expected results:
When running in VS Code, both calls to execSync should complete correctly.
Actual results:
The first call to execSync returns after completion, but there is still another process, displayed as Node.js Process 2 in the Call Stack window. This process doesn't have any debug controls. The only option is to disconnect. The second call to execSync is then attempted but doesn't seem to do anything. In the terminal, done format is printed and then there is no more displayed. If you press CTRL-C in the terminal window, the Process 2 process ends, but the main process is still active, even though you are returned to the command prompt.
VS Code version: Code 1.90.2 (5437499, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4200)
connor4312
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Jul 3, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Type: Bug
Reproduction available at: https://github.com/f8k8/VSCodeNPXBug
When running the project linked above using
Debug NPM script
, the first call toexecSync
doesn't seem to clean up properly and the second call hangs and is unable to be debugged. This only happens when the script is run from within VS Code. Running the script from the command prompt completes correctly.Steps to reproduce:
npm i
to install dependenciesnpm run run
. The script will complete correctly.Debug: Debug NPM script
.Expected results:
When running in VS Code, both calls to
execSync
should complete correctly.Actual results:
The first call to
execSync
returns after completion, but there is still another process, displayed asNode.js Process 2
in the Call Stack window. This process doesn't have any debug controls. The only option is to disconnect. The second call toexecSync
is then attempted but doesn't seem to do anything. In the terminal,done format
is printed and then there is no more displayed. If you press CTRL-C in the terminal window, theProcess 2
process ends, but the main process is still active, even though you are returned to the command prompt.VS Code version: Code 1.90.2 (5437499, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Extensions (4)
A/B Experiments
The text was updated successfully, but these errors were encountered: