TSServer exited. Code: null. Signal: SIGTERM when restarted, before restarting it's just stalling at "starting"

[othman316]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.74.3 & 175.0 (insider)
• OS Version: WSL Ubuntu on Windows 11 & on Windows 11
• TypeScript version: 4.9.4 & 5.0.0 dev

Steps to Reproduce:

1. Launch VS code, open a .ts file, go to TypeScript output
2. I get the following:
   

[mjbvz]

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

[vscodenpa]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

Happy Coding!

[othman316]

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

yes it does

[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

[vscodenpa]

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!