starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Running scripts crash when terminal (host) crashes, please keep 'm running! #14995

New Issue
Open
opened 2026-01-31 04:25:32 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:25:32 +00:00
Owner
Copy Link

Originally created by @Darkster1 on GitHub (Aug 28, 2021).

I'm coding some scripts that I run via this terminal app, it's great because having all running instances in one Window is easier then having multiple windows open.

But when the terminal crashes it takes all running scrips down with it.

Please allow running programs (like nodejs) to keep running when the terminal rans into an issue (in their own windows) instead of forcefully closing 'm all down.
I made a few save state functions that save the scripts state every now and then but even that isn't 100% because a few times the save files where left with "NULL"'s in there only.

I don't know when the terminal crashes it's quite Russian Roulette and there's no error message on screen usually when I see my mouse cursor change to the "loading one" I know what time it is... the last time I tried killing werfault.exe but sadly that didn't block / stop the terminal from being purged neither.

I like the terminal app but there are certainly a few things that need to be taken care off or I'd rather use multiple instances / windows of cmd open instead of having them in one window crashing.

I'd suggest a save state for running instances anyways cuz that would be best (for example when Windows decides to reboot (even when updates set to manual) it would be nice to resume where left off.

Originally created by @Darkster1 on GitHub (Aug 28, 2021). I'm coding some scripts that I run via this terminal app, it's great because having all running instances in one Window is easier then having multiple windows open. But when the terminal crashes it takes all running scrips down with it. Please allow running programs (like nodejs) to keep running when the terminal rans into an issue (in their own windows) instead of forcefully closing 'm all down. I made a few save state functions that save the scripts state every now and then but even that isn't 100% because a few times the save files where left with "NULL"'s in there only. I don't know when the terminal crashes it's quite Russian Roulette and there's no error message on screen usually when I see my mouse cursor change to the "loading one" I know what time it is... the last time I tried killing werfault.exe but sadly that didn't block / stop the terminal from being purged neither. I like the terminal app but there are certainly a few things that need to be taken care off or I'd rather use multiple instances / windows of cmd open instead of having them in one window crashing. I'd suggest a save state for running instances anyways cuz that would be best (for example when Windows decides to reboot (even when updates set to manual) it would be nice to resume where left off.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity Severity-Crash
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#14995
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?