typescript serivce crashed more than 5 times

[carlonoelle]

Issue Type: Bug

I have a Monorepo which uses yarn workspaces and typescript all the way, with root tsconfig which references all the tsconfigs from the multiple sub-packages. After some time the typescript service crashes multiple times and the warning is shown

VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:14:40.191Z) OS version: Darwin x64 20.3.0 Restricted Mode: No

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled| |Load (avg)|9, 9, 8| |Memory (System)|16.00GB (0.10GB free)| |Process Argv|--crash-reporter-id b878003a-371f-4e30-8cfe-13ad0c536d66| |Screen Reader|no| |VM|0%|

Extensions (44)

Extension|Author (truncated)|Version ---|---|--- aws-toolkit-vscode|ama|1.28.0 vscode-color|ans|0.4.5 cform|aws|0.0.24 task-panel|Bit|0.2.0 npm-intellisense|chr|1.4.0 path-intellisense|chr|2.4.0 gitignore|cod|0.7.0 bracket-pair-colorizer-2|Coe|0.2.1 dart-code|Dar|3.25.1 flutter|Dar|3.25.0 vscode-markdownlint|Dav|0.43.2 vscode-eslint|dba|2.1.23 xml|Dot|2.5.1 vscode-npm-script|eg2|0.3.22 prettier-vscode|esb|8.1.0 vscode-svelte-snippets|fiv|0.5.0 auto-rename-tag|for|0.1.8 shell-format|fox|7.1.0 terraform|has|2.14.0 svgeditor|hen|2.9.0 svelte-vscode|Jam|0.9.3 vscode-styled-components|jpo|1.6.6 fluent-icons|mig|0.0.12 dotenv|mik|1.0.1 vscode-docker|ms-|1.15.0 python|ms-|2021.8.1105858891 jupyter|ms-|2021.8.1195043623 awesome-flutter-snippets|Nas|3.0.1 color-highlight|nau|2.4.0 material-icon-theme|PKi|4.9.0 prisma|Pri|2.29.0 typescript-hero|rbb|3.0.0 vscode-commons|red|0.0.6 vscode-xml|red|0.18.0 vscode-yaml|red|0.22.0 js-jsx-snippets|sky|10.2.0 autoimport|ste|1.5.4 addDocComments|ste|0.0.8 vs-code-node-require|tgr|1.10.2 helm-intellisense|Tim|0.11.0 import-to-require|tle|0.7.0 vscode-todo-highlight|way|1.0.4 vscode-import-cost|wix|2.15.0 html-css-class-completion|Zig|1.20.0

A/B Experiments

``` vsliv368:30146709 vsreu685:30147344 python383cf:30185419 pythonvspyt678:30270856 pythonvspyt602:30300191 vspor879:30202332 vspor708:30202333 vspor363:30204092 pythonvspyt639:30300192 pythontb:30283811 pythonvspyt551:30345470 pythonptprofiler:30281270 vsdfh931cf:30280410 vshan820:30294714 vstes263cf:30335440 pythondataviewer:30285071 pythonvsuse255:30340121 vscod805:30301674 pythonvspyt200:30340761 vscextlang:30333561 binariesv615:30325510 vsccppwt:30329788 pythonvssor306:30344512 bridge0708:30335490 vstre464cf:30346473 ```

[vscodebot[bot]]

(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• TypeScript language service died unexpectedly 5 times in the last 5 minutes (#129950)

[mjbvz]

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

[machineghost]

Not OP, but I'm running on the latest insiders build, with all extensions disabled (on Linux), and am still getting this error basically as soon as I start up VS Code. Prior to my last update of VS Code this did not happen, so it's clearly a regression introduced in the last (non-insiders) update.

Here's my version info:

Version: 1.59.0 Commit: 379476f0e13988d90fab105c5c19e7abc8b1dea8 Date: 2021-08-04T23:13:20.182Z Electron: 13.1.7 Chrome: 91.0.4472.124 Node.js: 14.16.0 V8: 9.1.269.36-electron.0 OS: Linux x64 5.4.0-80-generic

P.S. I'm not using Typescript ... but I am using a jsconfig.json file with "checkJs": true,, so my VS Code utilizes TypeScript even though I don't. P.P.S. Happy to file a separate issue if needed (just let me know), but this seemed similar enough to my issue and didn't want to create duplicate issue spam.

[mjbvz]

@machineghost Yes please open a separate issue. Also be sure to test in VS Code insiders

[machineghost]

but I'm running on the latest insiders build

As I said, already running the latest Insiders build (just got it this morning). I'll file separately.

[mjbvz]

Closing as we need more information from the original poster to investigate