[error] TSServer exited. Code: null. Signal: SIGTERM on VSCode output - but Typescript still runs in the background

Personne n'a encore pris cette issue.

### 🔎 Search Terms

[error] TSServer exited. Code: null. Signal: SIGTERM

### 🕗 Version & Regression Information

- This is the behavior in every version I tried (5.8.3, 5..7.0)

### ⏯ Playground Link

_No response_

### 💻 Code

```ts
{
"compilerOptions": {
"target": "esnext",
"module": "esnext",
"lib": ["ES2023"],
"sourceMap": true,
"moduleResolution": "bundler",
"resolveJsonModule": true,
"isolatedModules": true,
"skipLibCheck": true,
"strict": true,
"allowJs": false,
"checkJs": false,
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"outDir": "build",
"rootDir": "src",
"baseUrl": ".",
"incremental": true,
"removeComments": true,
"noUnusedLocals": false,
"noUnusedParameters": true,
"verbatimModuleSyntax": true,
"paths": {
"@/*": ["src/*"]
}
},
"tsc-alias": {
"resolveFullPaths": true
},
"include": ["src/**/*.ts", "src/**/*.test.ts"],
"exclude": ["node_modules", "build"]
}

```

### 🙁 Actual behavior

I am getting [error] TSServer exited. Code: null. Signal: SIGTERM
Error on my Typescript Output in VSCode
But Typescript still works in the background - if const is not fulfilling interface I will get error about it.
I will also mention VScode is extreamly slow and I suspect one of the reason is that, and that there are multiple Typescript processes in the background.

### 🙂 Expected behavior

For the process to just be running normally

### Additional information about the issue

_No response_

Commencez par le tsconfig fourni et le message VSCode TypeScript Output, puis reproduisez SIGTERM avec les versions de TypeScript signalées. Déterminez si le processus TypeScript est arrêté de l’extérieur et si des processus en double subsistent ; le travail est terminé lorsque la cause est identifiée et que le comportement normal du processus sans l’erreur signalée est confirmé.

Rédigé par le modèle d'indexation à partir du texte de l'issue.