Restart TS server: TSServer exited. Code: null. Signal: SIGTERM

[shezhangzhang]

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

• VS Code Version:
  Version: 1.71.2
  Commit: 74b1f97
  Date: 2022-09-14T21:07:15.900Z
  Electron: 19.0.12
  Chromium: 102.0.5005.167
  Node.js: 16.14.2
  V8: 10.2.154.15-electron.0
  OS: Darwin arm64 21.6.0
  Sandboxed: No
• OS Version: Darwin arm64 21.6.0

Steps to Reproduce:

When I restart ts server, I got this error: "TSServer exited. Code: null. Signal: SIGTERM".
What's wrong here ? Or it's ok ？

[mjbvz]

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

[mjbvz]

Oh actually, if you're restarting SIGTERM is expected. It just means that the previous server process was terminated

[shezhangzhang]

Thanks.

[Manuelbaun]

I got the same error, but ts does not work after restart. When I hover over something it says (loading...)

[Info  - 11:33:48.360] <syntax> Forking...
[Info  - 11:33:48.375] <syntax> Starting...
[Info  - 11:33:48.375] <semantic> Forking...
[Info  - 11:33:48.391] <semantic> Starting...
[Error  - 11:33:48.451] TSServer exited. Code: null. Signal: SIGTERM

[FrameMuse]

When I try to put this option to "always"

TS Server stops working at all with the error:

[Info  - 11:49:53.558] Killing TS Server
[Info  - 11:49:53.558] Starting TS Server
[Info  - 11:49:53.558] Using tsserver from: /home/kotto/.vscode-server-insiders/bin/f4c58486f4a33b8c61f30a244374ef0d27dc19c3/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 11:49:53.558] <syntax> Forking...
[Info  - 11:49:53.564] <syntax> Starting...
[Error  - 11:49:53.567] TSServer exited. Code: null. Signal: SIGTERM

[IRediTOTO]

I usually have this error too. I don't know why it happened