microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.64k stars 29.05k forks source link

Node JS Debugger Error #159881

Closed samialateya closed 2 years ago

samialateya commented 2 years ago

Type: Bug

I tried to run the debugger and it's just did not start the server, it just freezed.

VS Code version: Code 1.71.0 (Universal) (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:25:38.437Z) OS version: Darwin arm64 21.6.0 Modes: Sandboxed: No

System Info |Item|Value| |---|---| |CPUs|Apple M1 Max (10 x 24)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|2, 2, 2| |Memory (System)|64.00GB (37.14GB free)| |Process Argv|. --crash-reporter-id 145012f6-e43a-4c0b-aa10-a420dbcbb7b3| |Screen Reader|no| |VM|0%|
Extensions (68) Extension|Author (truncated)|Version ---|---|--- better-comments|aar|3.0.2 codesnap|adp|1.3.4 toggle-block-comments|ale|1.3.0 laravel-extra-intellisense|ami|0.6.2 laravel-blade-spacer|aus|2.1.3 vscode-intelephense-client|bme|1.8.2 npm-intellisense|chr|1.4.2 vscode-sql-beautify|cla|0.3.15 laravel-goto-view|cod|1.3.7 dart-code|Dar|3.48.0 flutter|Dar|3.48.0 vscode-markdownlint|Dav|0.48.1 vscode-eslint|dba|2.2.6 javascript-ejs-support|Dig|1.3.1 es7-react-js-snippets|dsz|4.4.3 vscode-babel-coloring|dza|0.0.4 gitlens|eam|12.2.1 vscode-html-css|ecm|1.13.1 tslint|eg2|1.0.47 vscode-npm-script|eg2|0.3.28 prettier-vscode|esb|9.8.0 comment-anchors|Exo|1.9.6 auto-rename-tag|for|0.1.10 copilot|Git|1.43.6621 laravel-create-view|gli|0.0.6 php-awesome-snippets|hak|1.1.3 helium-icon-theme|hel|1.0.0 rest-client|hum|0.25.1 laravel-blade-wrapper|IHu|1.0.1 vue|jcb|0.1.5 JavaScriptSnippetsStandard|jms|1.8.0 auto-comment-blocks|kev|1.0.1 vscode-phpfmt|kok|1.0.31 php-namespace-resolver|Meh|1.1.9 vscode-language-babel|mgm|0.0.36 dotenv|mik|1.0.1 djlint|mon|2022.7.2 vscode-docker|ms-|1.22.1 remote-containers|ms-|0.252.0 vscode-typescript-tslint-plugin|ms-|1.3.4 laravel-goto-components|nao|1.2.0 vetur|oct|0.36.0 laravel-blade|one|1.32.0 laravel-extension-pack|one|1.1.0 laravel5-snippets|one|1.15.0 docker-compose|p1c|0.3.5 live-sass|rit|3.0.0 LiveServer|rit|5.7.9 nunjucks|ron|0.3.1 laravel-artisan|rya|0.0.28 vscode-javascript-booster|sbu|14.0.1 vue-vscode-snippets|sdr|3.1.1 vscode-blade-formatter|shu|0.17.3 js-jsx-snippets|sky|11.0.0 comment-divider|sta|0.4.0 autoimport|ste|1.5.4 code-spell-checker|str|2.7.0 svelte-vscode|sve|105.22.1 ayu|tea|1.0.5 volar|Vue|0.40.5 phaser-snippets|wuy|0.0.6 JavaScriptSnippets|xab|1.8.0 php-debug|xde|1.28.0 txt-syntax|xsh|0.2.0 vscode-yseopml|Yse|1.16.0 json|Zai|2.0.2 material-theme|zhu|3.15.2 html-css-class-completion|Zig|1.20.0 (4 theme extensions excluded)
A/B Experiments ``` vsliv368:30146709 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vslsvsres303:30308271 pythonvspyl392:30443607 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscoreces:30445986 pythondataviewer:30285071 vscod805:30301674 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 cmake_vspar411cf:30557515 vsaa593:30376534 pythonvs932:30410667 cppdebug:30492333 pylanb8912:30545647 vsclangdf:30486550 c4g48928:30535728 hb751961:30553087 dsvsc012cf:30540253 azure-dev_surveyone:30548225 2144e591:30553903 ```
YuriiBoikoOpn commented 2 years ago

the same on me. and 2 team members on VS code version 1.70 + working fine on vs code 1.71 for intel and M1 broken (for the same project )

nodejs +typescript +nestjs

weinand commented 2 years ago

/jsDebugLogs

vscodenpa commented 2 years ago

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

YuriiBoikoOpn commented 2 years ago

debug console doesn't show path to log. just show 1 line (with and without trace:true) /usr/loca/bin/node

info similar issue here https://github.com/microsoft/vscode/issues/159826

YuriiBoikoOpn commented 2 years ago

Screenshot 2022-09-02 at 17 22 08

YuriiBoikoOpn commented 2 years ago

@weinand^

urbenlegend commented 2 years ago

Same issue here. I can't launch any of the automatic debug configurations that start my npm scripts (npm start, etc.). They just get stuck with the same terminal output in @YuriiBoikoOpn 's screenshot.

connor4312 commented 2 years ago

@urbenlegend are you also on arm64/M1 macOS?

brokencrown commented 2 years ago

Same issue on Windows 10 Pro 21H2

connor4312 commented 2 years ago

Thanks, I can reproduce it. For now, you can create an entry in your launch.json that manually runs the script, like so:

{
  "type": "node-terminal",
  "request": "launch",
  "command": "npm run start"
}
connor4312 commented 2 years ago

Verification steps:

  1. Have a folder with npm scripts
  2. Under the debug dropdown or debug quick access, choose the "Node.js..." option
  3. Select and verify you can debug one of the npm scripts