VS Code Update Causes TypeScript Server Crashes with SIGTERM in GitHub Codespaces (VS Code 1.101.0)

[dbax825]

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

Summary:
TypeScript server consistently crashes with "TSServer exited. Code: null. Signal: SIGTERM" in GitHub Codespaces after the June 12, 2025 VS Code update (version 1.101.0).

Environment:
VS Code Version: 1.101.0 (June 12, 2025 release)
OS: GitHub Codespaces (Linux)
Node.js Version: v20.19.0
TypeScript Version: Tested with multiple versions (4.9.5, 5.x)
Extensions: Issue occurs even with all extensions disabled

Steps to Reproduce:
Open any TypeScript/JavaScript project in GitHub Codespaces
Wait for TypeScript server to start
Observe TypeScript is stuck at Starting...
Change TypeScript version OR Reload TypeScript Server
Observe immediate crash with SIGTERM

Expected Behavior:
TypeScript server should start normally and provide IntelliSense

Actual Behavior:
2025-06-15 15:51:21.650 [info] Starting TS Server
2025-06-15 15:51:21.650 [info] Using tsserver from: /workspaces/project/frontend/node_modules/typescript/lib/tsserver.js
2025-06-15 15:51:21.650 [info] Forking...
2025-06-15 15:51:21.650 [info] Starting...
2025-06-15 15:51:31.658 [info] Killing TS Server
2025-06-15 15:51:31.684 [error] TSServer exited. Code: null. Signal: SIGTERM

I have isolated this to VS Code's process management:
TypeScript server works perfectly when run directly:
bashnode /path/to/tsserver.js

Accepts commands and responds normally

Node.js child process forking works:
bashnode -e "const { fork } = require('child_process'); /* test code */"

Completes successfully without SIGTERM

Basic Node.js processes survive:
bashnode -e "setTimeout(() => console.log('alive'), 30000);"

Runs for full duration

Only VS Code's TypeScript integration crashes with SIGTERM

Timeline
Issue started immediately after June 12, 2025 VS Code update. Same codebase worked fine before this update. Multiple users are reporting similar issues.

Additional Context
Extension Host processes also crash with SIGTERM in logs. Issue affects both local TypeScript installations and VS Code's built-in version. I have tried different TypeScript versions, global installations, etc. - all fail the same way. Problem persists across different Codespace instances.
This appears to be a regression in VS Code's process management introduced in version 1.101.0, specifically affecting how child processes like TypeScript server are spawned/managed in remote environments like Codespaces.

[dbax825]

Relevant discussions about this in GitHub Community:
https://github.com/orgs/community/discussions/162690
https://github.com/orgs/community/discussions/162778

[michaelahern]

Have been attempting to debug this, as I've been having the same problem, and looks like it might be more related to #183765 and something with GitHub Codespaces. When going to a repo using the github.dev web-based editor, I see globalThis.crossOriginIsolated === true and the tsserver is doing full semantic checking. When going to the same repo using a GitHub Codespaces web-based editor, I see globalThis.crossOriginIsolated === false and the tsserver is only doing syntax checking. Both are running VS Code v1.101.0.

@dbax825 Can you see if your repo works using the github.dev editor?

[dbax825]

Have been attempting to debug this, as I've been having the same problem, and looks like it might be more related to #183765 and something with GitHub Codespaces. When going to a repo using the github.dev web-based editor, I see globalThis.crossOriginIsolated === true and the tsserver is doing full semantic checking. When going to the same repo using a GitHub Codespaces web-based editor, I see globalThis.crossOriginIsolated === false and the tsserver is only doing syntax checking. Both are running VS Code v1.101.0.

@dbax825 Can you see if your repo works using the github.dev editor?

Nailed it - TypeScript works fine in github.dev. I can see actual TypeScript errors in the Problems panel and get proper IntelliSense.

This is totally different from Codespaces where the TypeScript server crashes immediately with SIGTERM and nothing works.

[dbax825]

Have been attempting to debug this, as I've been having the same problem, and looks like it might be more related to #183765 and something with GitHub Codespaces. When going to a repo using the github.dev web-based editor, I see globalThis.crossOriginIsolated === true and the tsserver is doing full semantic checking. When going to the same repo using a GitHub Codespaces web-based editor, I see globalThis.crossOriginIsolated === false and the tsserver is only doing syntax checking. Both are running VS Code v1.101.0.

@dbax825 Can you see if your repo works using the github.dev editor?

where i disagree is it's related to #183765 as that's over a year old? this problem has only been for the last 3 days for me.

[rt-moura]

Any news on how can we fix this problem? Same here issue, TS Server crashes only on github codespaces, with the same repo, using local vs-code, it works just fine.

[michaelahern]

To clarify, I agree this isn't the precise issue as that and I started to see this Codespaces issue ~3-4 days ago as well. From stepping through the code path though, I suspect the root cause of our current issue might be related to Codespaces wiring up support for the crossOriginIsolated mode though..

[jeanp413]

PR fixing it here #251688