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

Terminal closes itself #3734

New Issue
Closed
opened 2026-01-30 23:28:42 +00:00 by claunia · 20 comments
claunia commented 2026-01-30 23:28:42 +00:00
Owner
Copy Link

Originally created by @xobs on GitHub (Sep 4, 2019).

Environment

Windows build number: Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): 0.4.2382.0

Any other software? WSL 16.04

Steps to reproduce

Use Terminal

Expected behavior

Terminal shouldn't close unless I tell it to close

Actual behavior

Terminal will occasionally pause for a few seconds, then close, taking with it all of my sessions. I am unsure whether this is a crash or not because it doesn't pop up a crash dialog box. This happens once every day or two.

For example, this just happened while doing a wget

If this is expected behavior, it's not good. If it's a crash, then it should present a dialog box indicating it's a crash, along with something such as a stack trace or crash reason.

Originally created by @xobs on GitHub (Sep 4, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): 0.4.2382.0 Any other software? WSL 16.04 ``` # Steps to reproduce Use Terminal # Expected behavior Terminal shouldn't close unless I tell it to close # Actual behavior Terminal will occasionally pause for a few seconds, then close, taking with it all of my sessions. I am unsure whether this is a crash or not because it doesn't pop up a crash dialog box. This happens once every day or two. For example, this just happened while doing a `wget` If this is expected behavior, it's not good. If it's a crash, then it should present a dialog box indicating it's a crash, along with something such as a stack trace or crash reason.
claunia commented 2026-01-30 23:28:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 4, 2019):

Yeah, that'll be a crash. Unfortunately, when we crash hard, it's somewhat out of our control as to whether we can pop up a dialog.

Would you mind collecting feedback hub info? (Following up with a tag that makes the bot tell you the good word.)

@DHowett-MSFT commented on GitHub (Sep 4, 2019): Yeah, that'll be a crash. Unfortunately, when we crash hard, it's somewhat out of our control as to whether we can pop up a dialog. Would you mind collecting feedback hub info? (Following up with a tag that makes the bot tell you the good word.)
claunia commented 2026-01-30 23:28:44 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 4, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Sep 4, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:28:44 +00:00
Author
Owner
Copy Link

@xobs commented on GitHub (Sep 4, 2019):

How do I send feedback? If I click the down-arrow and go to Feedback, it opens a browser and takes me to https://github.com/microsoft/Terminal/issues

@xobs commented on GitHub (Sep 4, 2019): How do I send feedback? If I click the down-arrow and go to Feedback, it opens a browser and takes me to https://github.com/microsoft/Terminal/issues
claunia commented 2026-01-30 23:28:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 4, 2019):

You'll need to use the Feedback Hub application (sorry, it's a separate app!) It'll help capture diagnostic information that Windows Terminal can't.

@DHowett-MSFT commented on GitHub (Sep 4, 2019): You'll need to use the Feedback Hub application (sorry, it's a separate app!) It'll help capture diagnostic information that Windows Terminal can't.
claunia commented 2026-01-30 23:28:45 +00:00
Author
Owner
Copy Link

@xobs commented on GitHub (Sep 4, 2019):

https://aka.ms/AA5zukj

@xobs commented on GitHub (Sep 4, 2019): https://aka.ms/AA5zukj
claunia commented 2026-01-30 23:28:45 +00:00
Author
Owner
Copy Link

@emc2314 commented on GitHub (Sep 8, 2019):

Same here. Suddenly exit about once a day. Sometimes using vim, sometimes running python. Don't know what's happening. For WSL, terminal crash means power off. Hope it will be fixed soon.

@emc2314 commented on GitHub (Sep 8, 2019): Same here. Suddenly exit about once a day. Sometimes using vim, sometimes running python. Don't know what's happening. For WSL, terminal crash means power off. Hope it will be fixed soon.
claunia commented 2026-01-30 23:28:45 +00:00
Author
Owner
Copy Link

@pcolmer commented on GitHub (Sep 13, 2019):

I'm experiencing Terminal just quitting on me at least once a day but, unfortunately, no particular pattern to it. My usage pattern is the default PowerShell terminal, a WSL terminal and then one or more SSH terminals.

More often than not, I think I have observed that quitting the SSH terminal with CTRL+D can trigger Terminal into dying.

@pcolmer commented on GitHub (Sep 13, 2019): I'm experiencing Terminal just quitting on me at least once a day but, unfortunately, no particular pattern to it. My usage pattern is the default PowerShell terminal, a WSL terminal and then one or more SSH terminals. More often than not, I think I have observed that quitting the SSH terminal with CTRL+D can trigger Terminal into dying.
claunia commented 2026-01-30 23:28:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 13, 2019):

This is the same bucket as /dupe #2248

@zadjii-msft commented on GitHub (Sep 13, 2019): This is the same bucket as /dupe #2248
claunia commented 2026-01-30 23:28:46 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 13, 2019):

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!

@ghost commented on GitHub (Sep 13, 2019): 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!
claunia commented 2026-01-30 23:28:46 +00:00
Author
Owner
Copy Link

@xobs commented on GitHub (Sep 14, 2019):

This seems different from #2248 -- that only happens when opening/closing tabs, whereas I'm experiencing this issue randomly. For example, in the initial bug report I mentioned that it happened while wget was in the middle of transferring files.

@xobs commented on GitHub (Sep 14, 2019): This seems different from #2248 -- that only happens when opening/closing tabs, whereas I'm experiencing this issue randomly. For example, in the initial bug report I mentioned that it happened while `wget` was in the middle of transferring files.
claunia commented 2026-01-30 23:28:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 18, 2019):

Well, that's certainly curious. If it crashes during a wget I'd assume that it's actually #2375, though when examining the feedback you sent, the stack was shockingly crashing in the same place as #2248. Maybe they're actually correlated with one another? Impossible to say for sure.

@zadjii-msft commented on GitHub (Sep 18, 2019): Well, that's certainly curious. If it crashes during a wget I'd assume that it's actually #2375, though when examining the feedback you sent, the stack was shockingly crashing in the same place as #2248. Maybe they're actually correlated with one another? Impossible to say for sure.
claunia commented 2026-01-30 23:28:47 +00:00
Author
Owner
Copy Link

@xobs commented on GitHub (Oct 5, 2019):

@zadjii-msft I just had this happen again. I was using riscv64-unknown-elf-gdb and I ran bt to get a backtrace.

@xobs commented on GitHub (Oct 5, 2019): @zadjii-msft I just had this happen again. I was using `riscv64-unknown-elf-gdb` and I ran `bt` to get a backtrace.
claunia commented 2026-01-30 23:28:47 +00:00
Author
Owner
Copy Link

@xobs commented on GitHub (Oct 7, 2019):

@zadjii-msft is there anything more I should do on this? If not, I'm going to stop using Terminal because having it close randomly when I'm typing characters is severely disruptive to working on terminal programs.

@xobs commented on GitHub (Oct 7, 2019): @zadjii-msft is there anything more I should do on this? If not, I'm going to stop using Terminal because having it close randomly when I'm typing characters is severely disruptive to working on terminal programs.
claunia commented 2026-01-30 23:28:47 +00:00
Author
Owner
Copy Link

@jiaulislam commented on GitHub (Jan 10, 2021):

any solution for this issue yet... now a days I'm facing same issue more frequently.

@jiaulislam commented on GitHub (Jan 10, 2021): any solution for this issue yet... now a days I'm facing same issue more frequently.
claunia commented 2026-01-30 23:28:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 21, 2021):

@jiaulislam The original bug that this issue was tracking was resolved more than a year ago. If you're still seeing the Terminal crash randomly on you, then there's probably something new that's the root cause of your issue. I'd recommend filing a new issue, and attaching a feedback hub link (like mentioned earlier in this thread).

@zadjii-msft commented on GitHub (Jan 21, 2021): @jiaulislam The original bug that this issue was tracking was resolved more than a year ago. If you're still seeing the Terminal crash randomly on you, then there's probably something new that's the root cause of your issue. I'd recommend filing a new issue, and attaching a feedback hub link (like mentioned earlier in this thread).
claunia commented 2026-01-30 23:28:48 +00:00
Author
Owner
Copy Link

@joeyjiaojg commented on GitHub (Oct 29, 2021):

I opened two windows terminals, and each opened several tabs.

When I'm using remote desktop of another windows machine connect the that host, the terminal window got disappeared.

Edition	Windows 10 Enterprise
Version	20H2
Installed on	‎6/‎3/‎2021
OS build	19042.1288
Experience	Windows Feature Experience Pack 120.2212.3920.0

Windows Terminal
Version: 1.10.2714.0
@joeyjiaojg commented on GitHub (Oct 29, 2021): I opened two windows terminals, and each opened several tabs. When I'm using remote desktop of another windows machine connect the that host, the terminal window got disappeared. ``` Edition Windows 10 Enterprise Version 20H2 Installed on ‎6/‎3/‎2021 OS build 19042.1288 Experience Windows Feature Experience Pack 120.2212.3920.0 ``` ``` Windows Terminal Version: 1.10.2714.0 ```
claunia commented 2026-01-30 23:28:48 +00:00
Author
Owner
Copy Link

@victoryhb commented on GitHub (Nov 24, 2022):

I can confirm that the same problem still persists in the the latest version of Windows Terminal (Version: 1.15.2875.0). The whole app just randomly disappears into nowhere after several hours in use.

@victoryhb commented on GitHub (Nov 24, 2022): I can confirm that the same problem still persists in the the latest version of Windows Terminal (Version: 1.15.2875.0). The whole app just randomly disappears into nowhere after several hours in use.
claunia commented 2026-01-30 23:28:48 +00:00
Author
Owner
Copy Link

@techierishi commented on GitHub (Mar 5, 2023):

Its still there in version 1.16.10262.0. Even on just using powershell, it closes automatically.

@techierishi commented on GitHub (Mar 5, 2023): Its still there in version `1.16.10262.0`. Even on just using powershell, it closes automatically.
claunia commented 2026-01-30 23:28:48 +00:00
Author
Owner
Copy Link

@RodrigoSaezCea commented on GitHub (Nov 17, 2023):

Its still there in version 1.18.2822.0

@RodrigoSaezCea commented on GitHub (Nov 17, 2023): Its still there in version 1.18.2822.0
claunia commented 2026-01-30 23:28:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 17, 2023):

Please read the thread. The original bug that this issue was tracking was resolved more than 3 years ago. If you're still seeing the Terminal crash randomly on you, then there's probably something new that's the root cause of your issue. I'd recommend filing a new issue, and attaching a feedback hub link (like mentioned earlier in this thread).

@zadjii-msft commented on GitHub (Nov 17, 2023): Please read the thread. The original bug that this issue was tracking was resolved more than 3 years ago. If you're still seeing the Terminal crash randomly on you, then there's probably something new that's the root cause of your issue. I'd recommend filing a new issue, and attaching a feedback hub link (like mentioned earlier in this thread).
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 Area-Quality Issue-Bug Product-Terminal Resolution-Duplicate 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#3734
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?