TS language server crashes repeatedly

[lokeshrj]

Type: Bug

TS language server crashes repeatedly

VS Code version: Code 1.91.0 (Universal) (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:54:18.541Z) OS version: Darwin arm64 23.5.0 Modes:

System Info

|Item|Value| |---|---| |CPUs|Apple M1 Pro (10 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| |Load (avg)|18, 14, 11| |Memory (System)|32.00GB (2.66GB free)| |Process Argv|/Users/Lokesh.Jagasia/sdmain/polaris/src/rubrik/spark-ui/spark-ui.code-workspace --crash-reporter-id fb3c1bd7-7989-4d28-9622-c33adedc8af0| |Screen Reader|no| |VM|0%|

Extensions (34)

Extension|Author (truncated)|Version ---|---|--- vscode-apollo|apo|1.20.0 vscode-eslint|dba|3.0.10 gitlens|eam|15.1.0 prettier-vscode|esb|10.4.0 figma-vscode-extension|fig|0.3.5 vscode-jest-runner|fir|0.4.73 copilot|Git|1.211.0 copilot-chat|Git|0.17.0 go|gol|0.41.4 vscode-jmespath|jos|0.0.6 debugpy|ms-|2024.6.0 isort|ms-|2023.10.1 pylint|ms-|2023.10.1 python|ms-|2024.8.1 vscode-pylance|ms-|2024.6.1 jupyter|ms-|2024.6.0 jupyter-keymap|ms-|1.1.2 jupyter-renderers|ms-|1.0.18 vscode-jupyter-cell-tags|ms-|0.1.9 vscode-jupyter-slideshow|ms-|0.1.6 remote-containers|ms-|0.375.0 remote-ssh|ms-|0.112.0 remote-ssh-edit|ms-|0.86.0 remote-wsl|ms-|0.88.2 vscode-remote-extensionpack|ms-|0.25.0 remote-explorer|ms-|0.4.3 remote-server|ms-|1.5.2 vsliveshare|ms-|1.0.5932 copy-json-path|nid|0.4.0 TidHelper|Non|0.1.2 vscode-statusbar-json-path|ric|2.0.0 scala|sca|0.5.7 vscode-json-path|wei|2.4.0 vscode-proto3|zxh|0.5.5

A/B Experiments

``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256860 vscod805cf:30301675 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 962ge761:30959799 pythongtdpath:30769146 welcomedialog:30910333 pythonnoceb:30805159 asynctok:30898717 pythonregdiag2:30936856 pythonmypyd1:30879173 h48ei257:31000450 pythontbext0:30879054 accentitlementst:30995554 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 jchc7451:31067544 chatpanelt:31048053 dsvsc021:30996838 724cj586:31013169 pythoncenvpt:31062603 a69g1124:31058053 dvdeprecation:31068756 dwnewjupyter:31046869 impr_priority:31082723 ```

[lokeshrj]

Also attempted with this reproduce latest VS Code insiders buildwith extensions disabled.

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