-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Closed
Labels
BugA bug in TypeScriptA bug in TypeScriptFix AvailableA PR has been opened for this issueA PR has been opened for this issue
Milestone
Description
Bug Report
When tsserver.js is started as a child process with --useNodeIpc command line switch included and the parent process is killed (with SIGKILL for example), the child process does not shutdown.
I have only tested this on recent 4.8.4 typescript version but I'm assuming that this issue exists since the --useNodeIpc flag was introduced in 4.6.0.
To reproduce this "in the wild" one can start VSCode, open some TS project to trigger typescript service initialization and then kill the parent of the tsserver process which is an extension process:
The tsserver process(es) keep running in the background.
🔎 Search Terms
tsserver ipc
🕗 Version & Regression Information
- This changed between versions 4.5.5 and 4.6.0
🙁 Actual behavior
The child tsserver process exits after parent process is killed.
🙂 Expected behavior
The child tsserver process keeps running in the background.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugA bug in TypeScriptA bug in TypeScriptFix AvailableA PR has been opened for this issueA PR has been opened for this issue
