TS Server fatal error: Debug Failure. False expression.

[PrAnAvBrAvE]

Type: Bug

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

TypeScript Version: 5.5.2

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 - Insiders 1.92.0-insider (3e283de567f5701a2be639bdacdac2c3cfdb088a, 2024-07-08T05:03:50.245Z) OS version: Windows_NT x64 10.0.22631 Modes:

System Info

|Item|Value| |---|---| |CPUs|11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz (4 x 2995)| |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| |Load (avg)|undefined| |Memory (System)|7.80GB (0.88GB free)| |Process Argv|--folder-uri file:///e%3A/ReactJs/textutils --crash-reporter-id 798abc3b-1c4b-45cb-9b07-46c9f2373633| |Screen Reader|no| |VM|0%|

Extensions (17)

Extension|Author (truncated)|Version ---|---|--- bootstrap5-vscode|Anb|0.4.4 vscode-tailwindcss|bra|0.12.5 es7-react-js-snippets|dsz|4.4.3 prettier-vscode|esb|10.4.0 auto-rename-tag|for|0.1.10 code-runner|for|0.12.2 debugpy|ms-|2024.10.0 python|ms-|2024.12.1 vscode-pylance|ms-|2024.7.1 cmake-tools|ms-|1.18.44 cpptools|ms-|1.21.5 cpptools-extension-pack|ms-|1.3.0 live-server|ms-|0.5.2024062701 makefile-tools|ms-|0.9.10 vscode-thunder-client|ran|2.24.13 LiveServer|rit|5.7.9 cmake|twx|0.0.17 (1 theme extensions excluded)

A/B Experiments

``` vsliv368:30146709 vspor879:30202332 vspor708:30202333 vspor363:30204092 vscod805cf:30301675 vsaa593:30376534 py29gd2263:31024238 c4g48928:30535728 a9j8j154:30646983 962ge761:30841072 pythongtdpath:30726887 welcomedialog:30812478 pythonnoceb:30776497 asynctok:30898717 dsvsc013:30777762 dsvsc014:30777825 dsvsc015:30821418 pythonregdiag2:30926734 pythonmypyd1:30859725 h48ei257:31000450 pythontbext0:30879054 accentitlementst:30870582 dsvsc016:30879898 dsvsc017:30880771 dsvsc018:30880772 cppperfnew:30980852 pythonait:30973460 bdiig495:31013172 a69g1124:31018687 dvdeprecation:31040973 dwnewjupyter:31046869 nb_pri_only:31057983 nativerepl1:31104042 refactort:31084545 pythonrstrctxt:31093868 hdi1a554:31091669 flighttreat:31105043 nativeloc1:31106922 ```

[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!