Typescript crashes in VS Code insiders latest build with all extensions disabled and TypeScript Nightly extension

[bennyk8y]

Hi, in our company we are working in relatively big TS monorepo.
For all our developers TS crashes few times a day.
My setup:

1. Visual Studio Code - Insiders - 1.75.0
2. JavaScript and TypeScript Nightly extension - latest
3. All extensions are disabled.

Another thing that we've tried is excluding from File Watcher node_modules/** and node_modules but i see its still being watched under, but i guess its a different thing.

Bug Report

🔎 Search Terms

typescript crash, typescript plugin loading infinitely

🕗 Version & Regression Information

Version: 1.75.0-insider
Commit: 243854703b7fa371abb752ec0df7817a615a308b
Date: 2023-01-13T08:04:47.712Z (1 wk ago)
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Darwin arm64 21.3.0
Sandboxed: Yes 

The indications for this crash are

1. Typescript icon loading infinitely
2. Hovering on any code have a ("loading...") indication
3. All Typescript features aren't working

[bennyk8y]

setting this in tsconfig.json

"exclude": ["**/node_modules", "node_modules"]

in every package in the monorepo should help?

[DanielRosenwasser]

Would you be able to provide us with a TSServer log from VS Code?

To do this, you'd need to:

1. Open up your command palette and either
   • open your global settings by entering Preferences: Open User Settings
   • open your local project by entering Preferences: Open Workspace Settings
2. Set the option "typescript.tsserver.log": "verbose",
3. Restart VS Code and reproduce the problem
4. In VS Code, run the TypeScript: Open TS Server log command
5. This should open the tsserver.log file.

⚠ Warning: A TSServer log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on GitHub, let us know and you can share the details privately.

[bennyk8y]

@DanielRosenwasser Hi!
I have it.
Can i share it privately?

[DanielRosenwasser]

Sure, email Myfirstname dot Mylastname at microsoft dot com

(capitalization unfortunately matters)

[DanielRosenwasser]

Just to clarify, this is more of a suspiciously long-running thing/a startup hang - it's not causing an actual crash, right?

[bennyk8y]

Yes, VSCode itself is not crashing, just TS features stop working after this happens, sometimes an error message pops with the message

The JS/TS language service crashed

[bennyk8y]

Just to clarify, all our development team that works on that repo (the main monorepo of the company) suffers from it, TS crashes few times a day.
Really not sure how can help VSCode understand not to watch node_modules, which i suspect affects the performance and maybe this somehow related to TS crashes.
But maybe the issue is not related to FileWatcher...

[bennyk8y]

@DanielRosenwasser did you get the email?