starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Run each window in a separate process #22891

New Issue
Closed
opened 2026-01-31 08:26:20 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:26:20 +00:00
Owner
Copy Link

Originally created by @olsner on GitHub (Feb 10, 2025).

Description of the new feature

When one terminal window crashes, it brings down every other terminal window on the computer since all windows are running from the same process. Personally, terminal windows are mission critical and it's bad enough to have a single one crash, let alone all of them at the same time.

Proposed technical implementation details

Start a new process for each opened window.

If really necessary add a setting to use shared processes for some possibly-maybe-memory-savings at the risk of losing more work?

Originally created by @olsner on GitHub (Feb 10, 2025). ### Description of the new feature When one terminal window crashes, it brings down every other terminal window on the computer since all windows are running from the same process. Personally, terminal windows are mission critical and it's bad enough to have a single one crash, let alone all of them at the same time. ### Proposed technical implementation details Start a new process for each opened window. If really necessary add a setting to use shared processes for some possibly-maybe-memory-savings at the risk of losing more work?
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixResolution-Won't-Fix labels 2026-01-31 08:26:20 +00:00
claunia commented 2026-01-31 08:26:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 10, 2025):

We actually used to do that! It was dramatically more complicated code, with tons of impossible to solve race conditions. And things like tab tear-out were neigh impossible to do without BOATLOADS of RPC for basically every input.

Moving everything into a single process happened in 1.18, and as of 1.23 all the windows get to live on the same thread too.

Now sure, this is not without its reliability concerns. But the codebase is dramatically easier to reason about with everything on one thread. I'd reckon it's easier to solve the situations leading to any crashes with the way things are structured currently. I'd rather just burn down existing sources of crashing (so that there's none at all), rather than trying to bring back all that RPC.

@zadjii-msft commented on GitHub (Feb 10, 2025): We actually used to do that! It was _dramatically_ more complicated code, with tons of impossible to solve race conditions. And things like tab tear-out were neigh impossible to do without BOATLOADS of RPC for basically every input. Moving everything into a single process happened in 1.18, and as of 1.23 all the windows get to live on the same thread too. Now sure, this is not without its reliability concerns. But the codebase is dramatically easier to reason about with everything on one thread. I'd reckon it's easier to solve the situations leading to any crashes with the way things are structured currently. I'd rather just burn down existing sources of crashing (so that there's none at all), rather than trying to bring back all that RPC.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Tag-Fix Needs-Triage Resolution-Won't-Fix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22891
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?