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

Terminal crashes/closes/terminates after being idle for a while #19197

New Issue
Closed
opened 2026-01-31 06:36:35 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 06:36:35 +00:00
Owner
Copy Link

Originally created by @ajhindle on GitHub (Jan 10, 2023).

Windows Terminal version

1.15.3466.0

Windows build number

10.0.22621.0

Other Software

Ubuntu 20.04.5 LTS
Powershell 5.1.22621.963

Steps to reproduce

Leave Terminal running idle for 1+ hours.
EDIT: This can also involve putting the computer to sleep for 1+ hours.

Expected Behavior

Terminal stays on for as long as I want it to

Actual Behavior

It shuts down by itself after 1+ hours running idle.

This didn't happen when I first started using Terminal about 18 months ago. I have upgraded to Windows 11 during that time - is it a coincidence?

The shutdown behaviour is annoying because I didn't tell it to shut down and I lose any work/environment I had running in Terminal.

Originally created by @ajhindle on GitHub (Jan 10, 2023). ### Windows Terminal version 1.15.3466.0 ### Windows build number 10.0.22621.0 ### Other Software Ubuntu 20.04.5 LTS Powershell 5.1.22621.963 ### Steps to reproduce Leave Terminal running idle for 1+ hours. EDIT: This can also involve putting the computer to sleep for 1+ hours. ### Expected Behavior Terminal stays on for as long as I want it to ### Actual Behavior It shuts down by itself after 1+ hours running idle. This didn't happen when I first started using Terminal about 18 months ago. I have upgraded to Windows 11 during that time - is it a coincidence? The shutdown behaviour is annoying because I didn't tell it to shut down and I lose any work/environment I had running in Terminal.
claunia added the Issue-BugResolution-DuplicateTracking-External labels 2026-01-31 06:36:35 +00:00
claunia commented 2026-01-31 06:36:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 10, 2023):

This sounds a lot like #12513. Can you check your "Background App Permissions" settings/?

If that doesn't seem to fix it, can you try following the steps in this post to set up automatic crash dumps? (For more info, see this link) If that works, then you should be able to automatically get a .dmp of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!

@zadjii-msft commented on GitHub (Jan 10, 2023): This sounds a lot like #12513. Can you check your ["Background App Permissions" settings](https://github.com/microsoft/terminal/issues/12513#issuecomment-1369795207)/? If that doesn't seem to fix it, can you try following the steps in [this post](https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm) to set up automatic crash dumps? (For more info, see [this link](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps)) If that works, then you should be able to automatically get a `.dmp` of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!
claunia commented 2026-01-31 06:36:36 +00:00
Author
Owner
Copy Link

@clor09 commented on GitHub (Jan 14, 2023):

This sounds a lot like #12513. Can you check your "Background App Permissions" settings/?

If that doesn't seem to fix it, can you try following the steps in this post to set up automatic crash dumps? (For more info, see this link) If that works, then you should be able to automatically get a .dmp of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!

hello~ I'm facing the same issue, and tried sereval methods from #12513 , but no lucky. i also set up crash dumps and got some .dmp files. em, how can i send the zipped dmp file to you guys~

@clor09 commented on GitHub (Jan 14, 2023): > This sounds a lot like #12513. Can you check your ["Background App Permissions" settings](https://github.com/microsoft/terminal/issues/12513#issuecomment-1369795207)/? > > If that doesn't seem to fix it, can you try following the steps in [this post](https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm) to set up automatic crash dumps? (For more info, see [this link](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps)) If that works, then you should be able to automatically get a `.dmp` of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks! hello~ I'm facing the same issue, and tried sereval methods from #12513 , but no lucky. i also set up crash dumps and got some .dmp files. em, how can i send the zipped dmp file to you guys~
claunia commented 2026-01-31 06:36:36 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jan 14, 2023):

@clor09 There are some instructions on how to send the dmp files here: https://github.com/microsoft/terminal/issues/14025#issuecomment-1372929445.

@j4james commented on GitHub (Jan 14, 2023): @clor09 There are some instructions on how to send the dmp files here: https://github.com/microsoft/terminal/issues/14025#issuecomment-1372929445.
claunia commented 2026-01-31 06:36:36 +00:00
Author
Owner
Copy Link

@clor09 commented on GitHub (Jan 16, 2023):

@j4james @zadjii-msft Thx, i uploaded the dmp file here: https://aka.ms/AAj7lag

@clor09 commented on GitHub (Jan 16, 2023): @j4james @zadjii-msft Thx, i uploaded the dmp file here: https://aka.ms/AAj7lag
claunia commented 2026-01-31 06:36:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 20, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jan 20, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 06:36:37 +00:00
Author
Owner
Copy Link

@Skesov commented on GitHub (Jan 20, 2023):

Have some problem with:
Windows 11 22621.1105
Windows Terminal Version: 1.15.3466.0

@Skesov commented on GitHub (Jan 20, 2023): Have some problem with: Windows 11 22621.1105 Windows Terminal Version: 1.15.3466.0
claunia commented 2026-01-31 06:36:37 +00:00
Author
Owner
Copy Link

@ajhindle commented on GitHub (Jan 22, 2023):

This sounds a lot like #12513. Can you check your "Background App Permissions" settings/?

If that doesn't seem to fix it, can you try following the steps in this post to set up automatic crash dumps? (For more info, see this link) If that works, then you should be able to automatically get a .dmp of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!

I looked at background app permissions and changed it "always" for Terminal - it was set to "power optimised".
Unfortunately that didn't work. I will get the dump files.

UPDATE 23-01-2023: so far I haven't had any dump files appear after several crashes/unsolicited terminations of Terminal.

UPDATE 25-01-2023: WER is still not producing any dump files for Terminal for me. It did give a dump file for RuntimeBroker so at least I know WER is working. Also I have noticed the same crashing/self-terminating behaviour for other Windows apps such as Calculator and Snipping Tool - both of those are still set to "power optimised" battery settings.

@ajhindle commented on GitHub (Jan 22, 2023): > This sounds a lot like #12513. Can you check your ["Background App Permissions" settings](https://github.com/microsoft/terminal/issues/12513#issuecomment-1369795207)/? > > If that doesn't seem to fix it, can you try following the steps in [this post](https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm) to set up automatic crash dumps? (For more info, see [this link](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps)) If that works, then you should be able to automatically get a `.dmp` of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks! I looked at background app permissions and changed it "always" for Terminal - it was set to "power optimised". Unfortunately that didn't work. I will get the dump files. UPDATE 23-01-2023: so far I haven't had any dump files appear after several crashes/unsolicited terminations of Terminal. UPDATE 25-01-2023: WER is still not producing any dump files for Terminal for me. It did give a dump file for RuntimeBroker so at least I know WER is working. Also I have noticed the same crashing/self-terminating behaviour for other Windows apps such as Calculator and Snipping Tool - both of those are still set to "power optimised" battery settings.
claunia commented 2026-01-31 06:36:37 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 25, 2023):

Thanks for the report. We're tracking this internally with MSFT-42831529.

@carlos-zamora commented on GitHub (Jan 25, 2023): Thanks for the report. We're tracking this internally with MSFT-42831529.
claunia commented 2026-01-31 06:36:37 +00:00
Author
Owner
Copy Link

@egvijayanand commented on GitHub (Feb 14, 2023):

Terminal instance auto terminates when the system goes to sleep. Observed in ver. 1.16.10262.0 Kindly fix this issue at the earliest.

Windows version - 10.0.22621.1194

@egvijayanand commented on GitHub (Feb 14, 2023): Terminal instance auto terminates when the system goes to sleep. Observed in ver. 1.16.10262.0 Kindly fix this issue at the earliest. Windows version - 10.0.22621.1194
claunia commented 2026-01-31 06:36:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 14, 2023):

You know what, we've actually got a better dupe in /dup #12513. That's got links to a pile of internal bugs. Thanks!

@zadjii-msft commented on GitHub (Feb 14, 2023): You know what, we've actually got a better dupe in /dup #12513. That's got links to a pile of internal bugs. Thanks!
claunia commented 2026-01-31 06:36:37 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 14, 2023):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 14, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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-Bug Resolution-Duplicate Tracking-External
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#19197
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?