TS Server fatal error: Debug Failure.

[eloi24]

Type: Bug

❗️❗️❗️ Please fill in the sections below to help us diagnose the issue ❗️❗️❗️

TypeScript Version: 5.7.0-dev.20240904

Steps to reproduce crash

1. 2. 3.

TS Server Log

❗️ Server logging disabled. To help us fix crashes like this, please enable logging by setting:

"typescript.tsserver.log": "verbose"

After enabling this setting, future crash reports will include the server log.

VS Code version: Code 1.93.0 (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:02:38.431Z) OS version: Windows_NT x64 10.0.19045 Modes:

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz (8 x 2304)| |GPU Status|2d_canvas: enabled
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
webnn: disabled_off| |Load (avg)|undefined| |Memory (System)|15.84GB (6.30GB free)| |Process Argv|--crash-reporter-id 901a9f3f-f5c4-4999-827f-ff464ae8c82c| |Screen Reader|no| |VM|0%|

Extensions (22)

Extension|Author (truncated)|Version ---|---|--- argutec-azure-repos|arg|1.2007.15 jsoncrack-vscode|Ayk|2.0.3 vscode-eslint|dba|3.0.13 emoji-snippets|dev|1.5.3 gitlens|eam|15.4.0 prettier-vscode|esb|11.0.0 copilot|Git|1.229.0 copilot-chat|Git|0.20.0 vscode-gutter-preview|kis|0.31.2 cpptools|ms-|1.21.6 remote-repositories|ms-|0.42.0 vscode-speech|ms-|0.10.0 vscode-typescript-next|ms-|5.7.20240904 vscode-versionlens|pfl|1.14.2 material-icon-theme|PKi|5.10.0 vscode-yaml|red|1.15.0 LiveServer|rit|5.7.9 even-better-toml|tam|0.19.2 errorlens|use|3.20.0 console-ninja|Wal|1.0.358 pretty-ts-errors|Yoa|0.6.0 material-theme|zhu|3.17.2

A/B Experiments

``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vscod805cf:30301675 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:31024239 vscaat:30438848 c4g48928:30535728 azure-dev_surveyone:30548225 2i9eh265:30646982 962ge761:30959799 pythongtdpath:30769146 welcomedialogc:30910334 pythonnoceb:30805159 asynctok:30898717 pythonmypyd1:30879173 h48ei257:31000450 pythontbext0:30879054 accentitlementst:30995554 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 dsvsc021:30996838 9c06g630:31013171 a69g1124:31058053 dvdeprecation:31068756 dwnewjupytercf:31046870 newcmakeconfigv2:31071590 impr_priority:31102340 refactort:31108082 pythonrstrctxt:31112756 flighttreat:31119336 wkspc-onlycs-t:31132770 wkspc-ranged-t:31125599 fje88620:31121564 ```

[mjbvz]

Please try collecting the TS Server log from the crashed instance:

1. Set "typescript.tsserver.log": "verbose"
2. Restart VS Code and reproduce the problem
3. Open the TypeScript section of the output panel

4. At the very top, find the first line that prints to path to the semantic error log file. It should look something like:

   [Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log

   That file contains the typescript logs.

Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out

⚠️Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

[vs-code-engineering[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!