Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spawned Node child process hangs when starting parent with debugger #95381

Closed
filipmares opened this issue Apr 15, 2020 · 8 comments
Closed

Spawned Node child process hangs when starting parent with debugger #95381

filipmares opened this issue Apr 15, 2020 · 8 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@filipmares
Copy link

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug

We have a main Electron Node process which we start with the debugger. It seems one of our child processes also gets the debugger attached and hangs when starting. This was repreoduced by verifying non-insider build doesn't hang.

VS Code version: Code - Insiders 1.45.0-insider (1c36d74, 2020-04-15T05:40:02.537Z)
OS version: Darwin x64 19.4.0

System Info
Item Value
CPUs Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Load (avg) 3, 3, 2
Memory (System) 32.00GB (6.84GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (13)
Extension Author (truncated) Version
vscode-browser-preview auc 0.6.6
color-info bie 0.5.1
gitlens eam 10.2.1
prettier-vscode esb 4.4.0
vscode-test-explorer hbe 2.18.0
rest-client hum 0.23.2
vscode-docker ms- 1.0.0
python ms- 2020.3.71659
azure-account ms- 0.8.9
vsliveshare ms- 1.0.1947
debugger-for-chrome msj 4.12.6
vscode-yaml red 0.7.2
vscode-sort-package-json uni 1.2.2

(2 theme extensions excluded)

@isidorn isidorn assigned roblourens and connor4312 and unassigned isidorn Apr 16, 2020
@isidorn isidorn added the debug Debug viewlet, configurations, breakpoints, adapter issues label Apr 16, 2020
@connor4312
Copy link
Member

connor4312 commented Apr 16, 2020

Do you have either of the settings debug.javascript.usePreview or debug.node.useV3 turned on to use our new debugger on Insiders?

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Apr 16, 2020
@filipmares
Copy link
Author

I do have one of those
"debug.javascript.usePreview": true,

Should I turn it off?

@connor4312
Copy link
Member

connor4312 commented Apr 17, 2020

Turning it off should fix the issue for you. I'll try to reproduce this tomorrow and, if successful, apply a fix to the preview debugger for tomorrow's nightly build.

@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Apr 17, 2020
@connor4312 connor4312 added this to the April 2020 milestone Apr 17, 2020
@filipmares
Copy link
Author

Thank you!

@connor4312
Copy link
Member

@filipmares can you provide your launch config for debugging and share how you're spawning the child process? Trying to reproduce this using the electron-quick-start repo with a dummy child process and our sample launch.json works for me.

@filipmares
Copy link
Author

Will DM on Teams. :)

@connor4312
Copy link
Member

This is similar to #95128, I put a workaround for in microsoft/vscode-js-debug@6538f20 that should resolve it. Please let me know if you run into more issues.

/duplicate #95128

@github-actions github-actions bot locked and limited conversation to collaborators Jun 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

5 participants
@filipmares @roblourens @isidorn @connor4312 and others