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

Windows Terminal crashes after trying to close tabs #7284

New Issue
Closed
opened 2026-01-31 00:59:59 +00:00 by claunia · 18 comments
claunia commented 2026-01-31 00:59:59 +00:00
Owner
Copy Link

Originally created by @avdain on GitHub (Apr 5, 2020).

Environment

Windows build number: 10.0.18363.752
Windows Terminal version (if applicable): 0.10.781.0

Any other software?

Steps to reproduce

  • Start Windows Terminal
  • Start more than 40+ tabs by pressing Ctrl and Shift + T
  • Now try to close the tabs as soon as possible

Expected behavior

  • Windows Terminal should not crash

Actual behavior

  • Windows Terminal crashes

ezgif-5-fcd68b503139

Originally created by @avdain on GitHub (Apr 5, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 10.0.18363.752 Windows Terminal version (if applicable): 0.10.781.0 Any other software? ``` # Steps to reproduce - Start Windows Terminal - Start more than 40+ tabs by pressing Ctrl and Shift + T - Now try to close the tabs as soon as possible <!-- A description of how to trigger this bug. --> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> - **Windows Terminal should not crash** # Actual behavior - **Windows Terminal crashes** ![ezgif-5-fcd68b503139](https://user-images.githubusercontent.com/47790579/78531333-81602780-77e5-11ea-8a25-3229e42c48da.gif) <!-- What's actually happening? -->
claunia added the Resolution-DuplicateProduct-TerminalSeverity-Crash labels 2026-01-31 00:59:59 +00:00
claunia commented 2026-01-31 01:00:01 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 6, 2020):

Hey could you file feedback using the Feedback hub so we could get a stack trace to investigate?

/feedback

@zadjii-msft commented on GitHub (Apr 6, 2020): Hey could you file feedback using the Feedback hub so we could get a stack trace to investigate? /feedback
claunia commented 2026-01-31 01:00:01 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 6, 2020):

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 (Apr 6, 2020): 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-31 01:00:02 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (Apr 6, 2020):

@zadjii-msft Should I include the link in the comment?

@avdain commented on GitHub (Apr 6, 2020): @zadjii-msft Should I include the link in the comment?
claunia commented 2026-01-31 01:00:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 6, 2020):

@Qantex yes please, it's basically impossible for us to find it without the link ☺️

@zadjii-msft commented on GitHub (Apr 6, 2020): @Qantex yes please, it's basically impossible for us to find it without the link ☺️
claunia commented 2026-01-31 01:00:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 6, 2020):

@Qantex That's just the link to this issue, not to the feedback 😄

@zadjii-msft commented on GitHub (Apr 6, 2020): @Qantex That's just the link to this issue, not to the feedback 😄
claunia commented 2026-01-31 01:00:03 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (Apr 6, 2020):

@zadjii-msft I thought you meant this section.

@avdain commented on GitHub (Apr 6, 2020): @zadjii-msft I thought you meant this section.
claunia commented 2026-01-31 01:00:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 6, 2020):

My dude, can you do this on your feedback?

That will make a aka.ms link, and then you can send that aka.ms link to us. 😄

@DHowett-MSFT commented on GitHub (Apr 6, 2020): My dude, can you do this on your feedback? ![](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png) That will make a `aka.ms` link, and then you can send that aka.ms link to us. :smile:
claunia commented 2026-01-31 01:00:04 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (Apr 6, 2020):

@DHowett Sure, I will now send a feedback via the feedback application.

@avdain commented on GitHub (Apr 6, 2020): @DHowett Sure, I will now send a feedback via the feedback application.
claunia commented 2026-01-31 01:00:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 6, 2020):

@Qantex ...

You need to

  1. Write a feedback item
  2. Copy the link FROM the feedback item
  3. Paste the link INTO github
  4. Submit the link TO github so that we can receive the link
@DHowett-MSFT commented on GitHub (Apr 6, 2020): @Qantex ... You need to 1. Write a feedback item 2. Copy the link FROM the feedback item 3. Paste the link INTO github 4. Submit the link TO github so that we can receive the link
claunia commented 2026-01-31 01:00:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 6, 2020):

image

image

@DHowett-MSFT commented on GitHub (Apr 6, 2020): ![image](https://user-images.githubusercontent.com/14316954/78592711-56cc9980-77fa-11ea-8947-978b0a1411a5.png) ![image](https://user-images.githubusercontent.com/14316954/78592728-5df3a780-77fa-11ea-8fe4-985b5e71ac53.png)
claunia commented 2026-01-31 01:00:05 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (Apr 7, 2020):

https://aka.ms/AA84d4u

@avdain commented on GitHub (Apr 7, 2020): https://aka.ms/AA84d4u
claunia commented 2026-01-31 01:00:05 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (Apr 7, 2020):

@zadjii-msft @DHowett I have now added the link in a comment and sent it.

@avdain commented on GitHub (Apr 7, 2020): @zadjii-msft @DHowett I have now added the link in a comment and sent it.
claunia commented 2026-01-31 01:00:06 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 7, 2020):

Thank you. We will continue the investigation.

@DHowett-MSFT commented on GitHub (Apr 7, 2020): Thank you. We will continue the investigation.
claunia commented 2026-01-31 01:00:06 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 8, 2020):

I can't reproduce this in v0.11, and it looks like it might have been a /dupe of #4613.

@DHowett-MSFT commented on GitHub (Apr 8, 2020): I can't reproduce this in v0.11, and it looks like it might have been a /dupe of #4613.
claunia commented 2026-01-31 01:00:06 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 8, 2020):

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 (Apr 8, 2020): 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-31 01:00:06 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (Apr 8, 2020):

@DHowett I have looked at the alleged duplicate and must say that my report is not a duplicate in my view.

I can't reproduce this in v0.11

To see the error from its own perspective, you need to train your timing.

@avdain commented on GitHub (Apr 8, 2020): @DHowett I have looked at the alleged duplicate and must say that my report is not a duplicate in my view. > I can't reproduce this in v0.11 To see the error from its own perspective, you need to train your timing.
claunia commented 2026-01-31 01:00:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 8, 2020):

#4613 fixed 13 different places where we would crash during the startup and shutdown of individual terminals. It is very likely, but not 100% certain, that it fixed this issue. 😄

@DHowett-MSFT commented on GitHub (Apr 8, 2020): #4613 fixed 13 different places where we would crash during the startup and shutdown of individual terminals. It is very likely, but not 100% certain, that it fixed this issue. 😄
claunia commented 2026-01-31 01:00:07 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 9, 2020):

This issue has been marked as duplicate and has not had any activity for 1 day. It will be closed for housekeeping purposes.

@ghost commented on GitHub (Apr 9, 2020): This issue has been marked as duplicate and has not had any activity for **1 day**. It will be closed for housekeeping purposes.
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 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#7284
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?