TS Server fatal error: Maximum call stack size exceeded

[abhishekicodelabs]

Type: Bug

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

TypeScript Version: 5.6.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 1.94.1 (Universal) (e10f2369d0d9614a452462f2e01cdc4aa9486296, 2024-10-05T05:44:32.189Z) OS version: Darwin arm64 23.4.0 Modes:

System Info

|Item|Value| |---|---| |CPUs|Apple M1 (8 x 2400)| |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
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off| |Load (avg)|2, 11, 12| |Memory (System)|8.00GB (0.05GB free)| |Process Argv|--crash-reporter-id ffd9080d-aee6-41a4-9ca3-96a6807ba9ef| |Screen Reader|no| |VM|0%|

Extensions (15)

Extension|Author (truncated)|Version ---|---|--- codeium|Cod|1.16.18 es7-react-js-snippets|dsz|4.4.3 gitlens|eam|15.6.0 prettier-vscode|esb|11.0.0 figma-vscode-extension|fig|0.3.5 vscode-power-mode|hoo|3.0.2 vs-color-picker|lih|1.0.0 debug-tracker-vscode|mcu|0.0.15 git-graph|mhu|1.30.0 color-highlight|nau|2.8.0 material-icon-theme|PKi|5.11.1 vscode-thunder-client|ran|2.27.6 LiveServer|rit|5.7.9 vscode-import-cost|wix|3.3.0 grammarly|znc|0.25.0 (1 theme extensions excluded)

A/B Experiments

``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256859 vscod805:30301674 binariesv615:30325510 vsaa593:30376534 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 2i9eh265:30646982 962ge761:30959799 pythongtdpath:30769146 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 724cj586:31013169 a69g1124:31058053 dvdeprecation:31068756 dwnewjupyter:31046869 2f103344:31071589 impr_priority:31102340 nativerepl1:31139838 refactort:31108082 pythonrstrctxt:31112756 flightc:31134773 wkspc-onlycs-t:31132770 wkspc-ranged-t:31151552 cf971741:31144450 defaultse:31146405 iacca2:31150323 notype1cf:31151524 controlgs:31153265 cc771715:31146322 ```

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