microsoft / vscode

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

VS Code crashes on launching a nodejs debugger #183456

Closed jshwek closed 10 months ago

jshwek commented 1 year ago

Type: Bug

Whenever I launch the debugger, about 7 out of 10 times it crashes. After it crashes, I cannot stop or restart the debugger (I've also tried terminating individual processes in CALL STACK).

I've tried the extension bisect and got the result saying that the issue could be likely VS Code and not an extension.

Below is what comes up in the Developer Tools console: Extension Host localProcessExtensionHost.ts:283 <--- Last few GCs --->[62724:00004C9400320000] 233900 ms: Mark-Compact (reduce) 3497.4 (3561.3) -> 3442.2 (3473.4) MB, 75.3 / 0.0 ms (average mu = 0.955, current mu = 0.839) last resort; GC in old space requested[62724:00004C9400320000] 233978 ms: Mark-Compact (reduce) 3442.2 (3473.4) -> 3441.9 (3462.9) MB, 77.8 / 0.0 ms (average mu = 0.882, current mu = 0.000) last resort; GC in old space requested<--- JS stacktrace --->[62724:0525/141036.968:ERROR:node_bindings.cc(164)] Fatal error in V8: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory abstractExtensionService.ts:637 Extension host (LocalProcess) terminated unexpectedly. Code: -1073741819, Signal: unknown pb @ abstractExtensionService.ts:637 pb @ nativeExtensionService.ts:163 ob @ abstractExtensionService.ts:629 (anonymous) @ abstractExtensionService.ts:607 invoke @ event.ts:862 deliver @ event.ts:1075 fire @ event.ts:1031 K @ localProcessExtensionHost.ts:478 (anonymous) @ localProcessExtensionHost.ts:291 invoke @ event.ts:862 deliver @ event.ts:1075 fire @ event.ts:1031 ee @ ipc.ts:672 t @ ipc.ts:740 s @ ipc.ts:729 (anonymous) @ ipc.ts:549 invoke @ event.ts:862 deliver @ event.ts:1075 fire @ event.ts:1031 ie @ event.ts:528 emit @ node:events:513 onMessage @ node:electron/js2c/renderer_init:2 log.ts:441 ERR Extension host (LocalProcess) terminated unexpectedly. No extensions were activated. log.ts:421 INFO Automatically restarting the extension host.

VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:39:26.248Z) OS version: Windows_NT x64 10.0.22621 Modes: Sandboxed: No

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz (20 x 3696)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|31.87GB (9.32GB free)| |Process Argv|--crash-reporter-id 12ad578d-f017-4b05-8653-a56d4067b0b1| |Screen Reader|yes| |VM|0%|
Extensions (40) Extension|Author (truncated)|Version ---|---|--- better-comments|aar|3.0.2 vscode-sql-formatter|adp|1.4.4 Bookmarks|ale|13.3.1 gitstash|art|5.2.0 es6-string-css|bas|0.1.0 http-status-codes|bea|1.0.5 path-intellisense|chr|2.8.4 regex|chr|0.4.0 vscode-markdownlint|Dav|0.50.0 vscode-eslint|dba|2.4.0 javascript-ejs-support|Dig|1.3.3 githistory|don|0.6.20 gitlens|eam|13.6.0 prettier-vscode|esb|9.13.0 auto-close-tag|for|0.5.14 auto-rename-tag|for|0.1.10 todo-tree|Gru|0.0.226 svg|joc|1.5.2 vscode-ejs|leo|1.0.6 ftp-sync|luk|0.3.9 rainbow-csv|mec|3.7.0 dotenv|mik|1.0.1 remote-ssh|ms-|0.102.0 remote-ssh-edit|ms-|0.86.0 powershell|ms-|2023.5.0 remote-explorer|ms-|0.4.0 vscode-js-profile-flame|ms-|1.0.5 copy-json-path|nid|0.3.0 vscode-thunder-client|ran|2.7.3 code-spell-checker|str|2.20.4 ejs-snippets|Tao|0.1.0 es6-string-html|Tob|2.12.1 intellicode-api-usage-examples|Vis|0.2.7 vscodeintellicode|Vis|1.2.30 vscode-icons|vsc|12.4.0 JavaScriptSnippets|xab|1.8.0 php-pack|xde|1.0.3 vscode-surround|yat|1.5.0 json|Zai|2.0.2 html-css-class-completion|Zig|1.20.0
A/B Experiments ``` vsliv368:30146709 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vslsvsres303:30308271 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscorecescf:30445987 vscod805:30301674 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 cmake_vspar411:30581797 vsaa593cf:30376535 pythonvs932:30410667 cppdebug:30492333 vscaat:30438848 vsclangdc:30486549 c4g48928:30535728 dsvsc012:30540252 pynewext54:30695312 azure-dev_surveyone:30548225 3biah626:30602489 pyind779:30671433 89544117:30613380 pythonsymbol12:30671437 a9j8j154:30646983 showlangstatbar:30737416 vsctsb:30748421 pythonms35:30701012 0bg3d529:30706074 pythonfmttext:30731395 fixshowwlkth:30730052 showsbindicator:30730056 pythongtdpath:30739704 ```
jshwek commented 1 year ago

This only happens for a specific (Node.js) project. I've never seen it crash for any other projects.

roblourens commented 1 year ago

Can you try to grab a trace?

/jsDebugLogs

vscodenpa commented 1 year 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

jshwek commented 1 year ago

Please see attached, many thanks in advance. vscode-debugadapter-040ce276.json.gz

connor4312 commented 1 year ago

Thanks for the logs. They look mostly normal, but something suspicious I see is that the debugger is trying to parse sourcemaps from a bunch of non-sourcemap files in public/libs, such as public\libs\animate-on-scroll\animate-on-scroll.js. I suspect the crash might be related to some of the weirdness it's running into in that folder, but I'm not sure. The stacktrace reported in the debug console is unfortunately not very useful 😞

Are you able to share all or part of your project with me? At minimum, a .zip of the public/libs folder would be useful for me to try to reproduce if my hypothesis is correct.

jshwek commented 1 year ago

Hi @connor4312 and thanks for the update.

I'm using an admin template for this project that can be found here

See below for the zipped /dist folder which contains all the css, js, libs and fonts (and which I used). dist.zip

Please let me know if there's anything else I can provide and thanks again!

jshwek commented 1 year ago

Hi just checking if there's anything else you need?

thisiswhereitype commented 1 year ago

I am getting this error code on start which I initally reported here but now see this when running C:\Users\Joe> code --disable-extensions ~although adding --verbose appears to suppress the issue~ but only for a bit.

When running with extensions and not immediately crashing I noticed:

  1. Opening extensions view triggered this instantly twice.
Version: 1.82.2 (user setup)
Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Date: 2023-09-14T05:55:25.390Z
Electron: 25.8.1
ElectronBuildId: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045
vscodenpa commented 10 months ago

Hey @connor4312, this issue might need further attention.

@jshwek, you can help us out by closing this issue if the problem no longer exists, or adding more information.

connor4312 commented 10 months ago

Unfortunately I haven't been able to trigger the crash in those files 😕 and so far I haven't had any other reports of such a crash, so I don't have a lot to go on. Any additional you can provide / a full repo would be helpful. You can also make a private repo and invite me to it if you aren't comfortable publishing something publicly.

jshwek commented 10 months ago

It actually hasn't happened to me in some time.

I'm guessing that an update went up that fixed my issue either directly or indirectly.

On Fri, Dec 8, 2023, 7:54 PM Connor Peet @.***> wrote:

Unfortunately I haven't been able to trigger the crash in those files 😕 and so far I haven't had any other reports of such a crash, so I don't have a lot to go on. Any additional you can provide / a full repo would be helpful. You can also make a private repo and invite me to it if you aren't comfortable publishing something publicly.

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/183456#issuecomment-1848021077, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARBTYISUHWAAK7KJYDGI22DYIOZDHAVCNFSM6AAAAAAYPGNUL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYGAZDCMBXG4 . You are receiving this because you were mentioned.Message ID: @.***>

connor4312 commented 10 months ago

Thanks for letting me know. I'll close the issue for now, please follow up if you see it again!