Bug in VSCode and Typescript - TSServer exited. Code: null. Signal: SIGTERM - Even on empty project while tsc build works

[eliezra236]

Type: Bug

Whenever I try to launch a typescript project, even a complexly empty one I am getting the same Error in my output even after restarting ts server.
I created this simple "project" with nothing, the error even occors here.
https://github.com/eliezra236/ts-test

This is the tsconfig

{
    "compilerOptions": {
        "target": "esnext",
        "module": "esnext",
        "lib": [
            "ES2023",
            "dom"
        ],
        "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",
    ],
}

2025-08-26 10:40:01.646 [info] Killing TS Server
2025-08-26 10:40:01.646 [info] Starting TS Server
2025-08-26 10:40:01.646 [info] Using tsserver from: /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
2025-08-26 10:40:01.646 [info] <syntax> Forking...
2025-08-26 10:40:01.646 [info] <syntax> Starting...
2025-08-26 10:40:01.646 [info] <semantic> Forking...
2025-08-26 10:40:01.647 [info] <semantic> Starting...
2025-08-26 10:40:01.656 [error] TSServer exited. Code: null. Signal: SIGTERM

Even with the mock "project' I created that only has a single file the problem still persist

VS Code version: Code 1.103.2 (Universal) (6f17636121051a53c88d3e605c491d22af2ba755, 2025-08-20T16:45:34.255Z)
OS version: Darwin arm64 24.6.0
Modes:

System Info

Item	Value
CPUs	Apple M4 (10 x 2400)
GPU Status	2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: enabled_on trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	2, 2, 2
Memory (System)	16.00GB (0.53GB free)
Process Argv
Screen Reader	no
VM	0%

Extensions (21)

Extension	Author (truncated)	Version
Bookmarks	ale	13.5.0
vscode-tailwindcss	bra	0.14.26
path-intellisense	chr	2.10.0
vscode-css-modules	cli	0.5.4
postcss	css	1.0.9
vscode-eslint	dba	3.0.16
gitlens	eam	17.4.0
prettier-vscode	esb	11.0.0
auto-rename-tag	for	0.1.10
copilot	Git	1.350.0
copilot-chat	Git	0.30.3
vscode-pull-request-github	Git	0.116.1
todo-tree	Gru	0.0.226
prettify-json	moh	0.0.3
material-icon-theme	PKi	5.26.0
LiveServer	rit	5.7.9
code-spell-checker	str	4.0.47
sass-indented	syl	1.8.33
sort-lines	Tyr	1.12.0
pretty-ts-errors	Yoa	0.6.1
material-theme	zhu	3.19.0

(1 theme extensions excluded)

[mjbvz]

@andrewbranch Only thing in the log suggests that maybe it's related to the typings installer. Are there any unhandled exceptions related to that that could crash the entire server?

@eliezra236 Thanks for the issue. Does this reproduce with all extensions disabled too? I couldn't reproduce this on Mac

Also please try setting "typescript.disableAutomaticTypeAcquisition": true to see if that stops the crash

[andrewbranch]

I've never seen this before. @sheetalkamat any ideas?

[eliezra236]

@mjbvz

Thank you.
I have tried to do restart with extension disabled, the problem still happened.
Also tried settings "typescript.disableAutomaticTypeAcquisition": true
It still happened

[sheetalkamat]

i dont see this happening by cloning and opening vscode either

[Megabyteceer]

I spend 3 days attempting to fix SIGTERM issue i startet to have just after vscode update to 1.103.2.

I have installed many vscode versoins one by one with no extensions, but SIGTERM happens every of them.

In my case SIGTERM happens on existing project, worked well on older vscode. Just now i have opened the project, it worked well for a minute, and then imports become red. I did TS server restart command and then got SIGTERM. Link to logs:
https://pixel-cave.com/ts.crash.logs.zip

{
  "compilerOptions": {
    "target": "ES2020",
    "useDefineForClassFields": true,
    "module": "ESNext",
    "lib": [
      "ES2020",
      "DOM",
      "DOM.Iterable"
    ],
    /* Bundler mode */
    "moduleResolution": "bundler",
    "skipLibCheck": true,
    "skipDefaultLibCheck": true,
    "allowImportingTsExtensions": true,
    "resolveJsonModule": false,
    "isolatedModules": false,
    "noEmit": true,
    "forceConsistentCasingInFileNames": true,
    "allowSyntheticDefaultImports": true,
    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    "experimentalDecorators": true,
    "baseUrl": ".",
    "types": [
      "pixi.js"
    ]
  },
  "exclude": [
    "node_modules"
  ],
  "include":["**/*.mjs","./games/flight/Aviamasters/","./games/flight/shared-lib","./libs/thing-games-utils/common","./libs/thing-games-utils/common-ui","./libs/thing-games-utils/common-ui-casual","thing-editor/src"]
}

[eliezra236]

@sheetalkamat

I do think it's a local issue, do you have a clue what setting might cause it?

[Megabyteceer]

@sheetalkamat @eliezra236 Sorry for bother you. I Realize that i is 'restart-tsserver-on-config-change' extnsion kills tsserver.

[eliezra236]

@Megabyteceer Thank you.
Where do you see this setting?

[Megabyteceer]

@eliezra236 this extension caused SIGTERM in my case. https://marketplace.visualstudio.com/items?itemName=neotan.vscode-auto-restart-typescript-eslint-servers

[eliezra236]

@Megabyteceer I had this extension in the past, but I uninstalled it, maybe it has some traces