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

Nobody has claimed this yet.

### 🔎 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_

Begin with the provided tsconfig and the VSCode TypeScript Output message, then reproduce the SIGTERM across the reported TypeScript versions. Determine whether the TypeScript process is being terminated externally and whether duplicate processes remain; done means identifying the cause and confirming normal process behavior without the reported error.

Written by the indexing model from the issue text.