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

Windows Terminal crashes when opening a second tab #23264

New Issue
Closed
opened 2026-01-31 08:37:08 +00:00 by claunia · 30 comments
claunia commented 2026-01-31 08:37:08 +00:00
Owner
Copy Link

Originally created by @RC51Owner on GitHub (May 17, 2025).

Windows Terminal version

1.22.11141.0

Windows build number

10.0.26100.4061

Other Software

WSL2 Ubuntu 18.04.06LTS BASH

Steps to reproduce

Two issues:

  1. I have updated the Ubuntu 18.04.6 LTS > Appearance to use the Ubuntu-18-04- color scheme, but when I run Terminal (Ububtu-18.04.6 LTS is the default terminal type) it display using the Default Cambell color schem
  2. With one Ububut 18.04.6 LTS terminal open, I try and open another terminal (it doesn't matter if it is a Ubuntu or any other supported type - command or powershell) the existing terminal window briefly flashes an empty border and then disappears. When I try and launch Terminal nothing appears to happen. I have to reboot the machine to get Terminal to show the Ubuntu bash shell

I have tried repairing, restarting, uninstalling and re-installing Terminal to no avail. I have also tried using the Terminal App Preview installation and it behaves the same as the release version.

I do not have MacType installed :)

Regards,

Mark

Expected Behavior

  1. That the chosen colour scheme would be used for the Ubuntu bash shell
  2. That I can open multiple terminal types and they would display correctly and be usable.

Actual Behavior

  1. Default Terminal colour scheme used instead of specifically defined one for the terminal type
  2. Terminal crashes and display no other terminals until I reboot the machin
Originally created by @RC51Owner on GitHub (May 17, 2025). ### Windows Terminal version 1.22.11141.0 ### Windows build number 10.0.26100.4061 ### Other Software WSL2 Ubuntu 18.04.06LTS BASH ### Steps to reproduce Two issues: 1. I have updated the Ubuntu 18.04.6 LTS > Appearance to use the Ubuntu-18-04- color scheme, but when I run Terminal (Ububtu-18.04.6 LTS is the default terminal type) it display using the Default Cambell color schem 2. With one Ububut 18.04.6 LTS terminal open, I try and open another terminal (it doesn't matter if it is a Ubuntu or any other supported type - command or powershell) the existing terminal window briefly flashes an empty border and then disappears. When I try and launch Terminal nothing appears to happen. I have to reboot the machine to get Terminal to show the Ubuntu bash shell I have tried repairing, restarting, uninstalling and re-installing Terminal to no avail. I have also tried using the Terminal App Preview installation and it behaves the same as the release version. I do not have MacType installed :) Regards, Mark ### Expected Behavior 1. That the chosen colour scheme would be used for the Ubuntu bash shell 2. That I can open multiple terminal types and they would display correctly and be usable. ### Actual Behavior 1. Default Terminal colour scheme used instead of specifically defined one for the terminal type 2. Terminal crashes and display no other terminals until I reboot the machin
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-AttentionSeverity-Crash labels 2026-01-31 08:37:09 +00:00
claunia commented 2026-01-31 08:37:10 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 19, 2025):

Is there some log that I can attach to help debug this issue?

@RC51Owner commented on GitHub (May 19, 2025): Is there some log that I can attach to help debug this issue?
claunia commented 2026-01-31 08:37:11 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 19, 2025):

One other piece of information, the same behaviour happens when I open a PowerScript command window or a older command window. So this is not a WSL specific issue. The chosen colour scheme is not applied and if I try and open a second terminal the terminal application disappears

@RC51Owner commented on GitHub (May 19, 2025): One other piece of information, the same behaviour happens when I open a PowerScript command window or a older command window. So this is not a WSL specific issue. The chosen colour scheme is not applied and if I try and open a second terminal the terminal application disappears
claunia commented 2026-01-31 08:37:11 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 20, 2025):

On my reboot yesterday, it appears now that the Ubuntu shell in Terminal APP uses the correct colour scheme. I haven't yet tried to instantiate a second shell as I need to do work and don't want to disrupt that.

@RC51Owner commented on GitHub (May 20, 2025): On my reboot yesterday, it appears now that the Ubuntu shell in Terminal APP uses the correct colour scheme. I haven't yet tried to instantiate a second shell as I need to do work and don't want to disrupt that.
claunia commented 2026-01-31 08:37:11 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 21, 2025):

Had the opportunity to restart my system and it still works when I open Terminal it pulls up my default Ubuntu 18.04.6LTS Bash shell with the correct colour schema and if I open up another instance (using the '+' shortcut on the title bar another instance successfully opens with the same schema. It no longer crashes the system.

I don't know what "fixed" it?

@RC51Owner commented on GitHub (May 21, 2025): Had the opportunity to restart my system and it still works when I open Terminal it pulls up my default Ubuntu 18.04.6LTS Bash shell with the correct colour schema and if I open up another instance (using the '+' shortcut on the title bar another instance successfully opens with the same schema. It no longer crashes the system. I don't know what "fixed" it?
claunia commented 2026-01-31 08:37:11 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 24, 2025):

I added a bunch of other comments.... where did they go? Looks like the comments are reverse order sorted and I didn't seem them below the issue comment...

I am now back to it not working after it worked for a while. I reset the EC Controller and it seems to have "broken" something. Trying to fix a Parked CPU problem and it breaks the terminal issue. Grrrr.

Just noticed that Window PowerShell uses the correct colour scheme

Mark

@RC51Owner commented on GitHub (May 24, 2025): I added a bunch of other comments.... where did they go? Looks like the comments are reverse order sorted and I didn't seem them below the issue comment... I am now back to it not working after it worked for a while. I reset the EC Controller and it seems to have "broken" something. Trying to fix a Parked CPU problem and it breaks the terminal issue. Grrrr. Just noticed that Window PowerShell uses the correct colour scheme Mark
claunia commented 2026-01-31 08:37:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Looks like you had quite a journey debugging this one! Can you share your settings.json file and perhaps a couple screenshots?

@DHowett commented on GitHub (May 28, 2025): Looks like you had quite a journey debugging this one! Can you share your `settings.json` file and perhaps a couple screenshots?
claunia commented 2026-01-31 08:37:12 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

@DHowett let me see if I an figure out where the settings.json file for the Terminal App is located. I dragged and dropped it into the window - hopefully you can see it.

settings.json

In the meantime let me put together some screen shots

My settings from Windows Terminal App for Ubuntu 18.04.6 LTS. Note that the Color scheme is Ubuntu-18.04-... which has a purple back ground.

Image

How it is displayed:

Image

Which looks to be the Default Appearance:

Image

My Startup settings:

Image

And here is the App Execution Aliases:

Image

@RC51Owner commented on GitHub (May 28, 2025): @DHowett let me see if I an figure out where the settings.json file for the Terminal App is located. I dragged and dropped it into the window - hopefully you can see it. [settings.json](https://github.com/user-attachments/files/20494422/settings.json) In the meantime let me put together some screen shots My settings from Windows Terminal App for Ubuntu 18.04.6 LTS. Note that the Color scheme is Ubuntu-18.04-... which has a purple back ground. ![Image](https://github.com/user-attachments/assets/8b2e3046-b360-4d0c-a617-18d3a5e2042c) How it is displayed: ![Image](https://github.com/user-attachments/assets/8ffa2af8-7c23-44da-9159-87bde8a88d9b) Which looks to be the Default Appearance: ![Image](https://github.com/user-attachments/assets/f564ab2d-1952-4f6c-8741-7ffc451402e0) My Startup settings: ![Image](https://github.com/user-attachments/assets/19cdcb6d-4204-43eb-9d8a-d7bf9ea42a57) And here is the App Execution Aliases: ![Image](https://github.com/user-attachments/assets/2c4f7ebe-3c8f-4ee5-924f-6572addc42f4)
claunia commented 2026-01-31 08:37:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Oh, you know what? This is a specific case of #12961. Terminal cannot tell that ubuntu.exe and wsl.exe -d Ubuntu (for any given set of version numbers) are actually the same application. Depending on how you launch it, it gets different settings because all Terminal gets to see is the EXE filename...

This is something that hopefully we can improve by working with the WSL team but for now, /dup #12961.

If you're using WSL more "exclusively," you may be able to work around it by setting the default color scheme to the Ubuntu one (Defaults->Appearance), and then setting each non-WSL profile to whatever other scheme you want. Not ideal, but neither is any of this!

@DHowett commented on GitHub (May 28, 2025): Oh, you know what? This is a specific case of #12961. Terminal cannot tell that `ubuntu.exe` and `wsl.exe -d Ubuntu` (for any given set of version numbers) are actually the same application. Depending on how you launch it, it gets different settings because all Terminal gets to see is the EXE filename... This is something that hopefully we can improve by working with the WSL team but for now, /dup #12961. If you're using WSL more "exclusively," you may be able to work around it by setting the default color scheme to the Ubuntu one (Defaults->Appearance), and then setting each non-WSL profile to whatever other scheme you want. Not ideal, but neither is any of this!
claunia commented 2026-01-31 08:37:12 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

@DHowett that is one half of the issue resolved - what about it crashing when trying to open a second instance of a Ubuntu Bash shell?

I have also noticed that I need to open the Bash shell directly rather than launching Terminal. If I launch Terminal then no Ubuntu Bash shell is displayed (even though it is set as my default Terminal type).

@RC51Owner commented on GitHub (May 28, 2025): @DHowett that is one half of the issue resolved - what about it crashing when trying to open a second instance of a Ubuntu Bash shell? I have also noticed that I need to open the Bash shell directly rather than launching Terminal. If I launch Terminal then no Ubuntu Bash shell is displayed (even though it is set as my default Terminal type).
claunia commented 2026-01-31 08:37:13 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Can you go into the Settings for that profile and grab the Command line?

@DHowett commented on GitHub (May 28, 2025): Can you go into the Settings for that profile and grab the `Command line`?
claunia commented 2026-01-31 08:37:13 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

Image

@RC51Owner commented on GitHub (May 28, 2025): ![Image](https://github.com/user-attachments/assets/f4d6646f-3ebe-4b91-bcc2-843559d36e66)
claunia commented 2026-01-31 08:37:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Iiinteresting. Do you by chance have an "ubuntu1804.exe" in your app execution aliases list as well?

@DHowett commented on GitHub (May 28, 2025): Iiinteresting. Do you by chance have an "ubuntu1804.exe" in your app execution aliases list as well?
claunia commented 2026-01-31 08:37:14 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

I do:

Image

@RC51Owner commented on GitHub (May 28, 2025): I do: ![Image](https://github.com/user-attachments/assets/27d4c507-f75d-4284-b00f-e2fb535e00c2)
claunia commented 2026-01-31 08:37:14 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

Should it be something else other than ubuntu1804.exe?

@RC51Owner commented on GitHub (May 28, 2025): Should it be something else other than ubuntu1804.exe?
claunia commented 2026-01-31 08:37:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Nah, that seems right.

Got another question though. Ubuntu > Advanced > "Profile Termination Behavior"

If you change that to "Never close automatically," what happens when you would otherwise have seen a crash?

@DHowett commented on GitHub (May 28, 2025): Nah, that seems right. Got another question though. Ubuntu > Advanced > "Profile Termination Behavior" If you change that to "Never close automatically," what happens when you would otherwise have seen a crash?
claunia commented 2026-01-31 08:37:15 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

The process is for me to have a running Ubuntu Bash and the select the "+" next to the running shell and it thinks about it for a while and then the terminal app shuts down. This is still true when I set the termination behaviour to be "Never close automatically"

@RC51Owner commented on GitHub (May 28, 2025): The process is for me to have a running Ubuntu Bash and the select the "+" next to the running shell and it thinks about it for a while and then the terminal app shuts down. This is still true when I set the termination behaviour to be "Never close automatically"
claunia commented 2026-01-31 08:37:15 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

I see that Ubuntu 18.04.6 LTS seems to chain to Ubuntu-18.04 settings which uses this for the command line:

Image

@RC51Owner commented on GitHub (May 28, 2025): I see that Ubuntu 18.04.6 LTS seems to chain to Ubuntu-18.04 settings which uses this for the command line: ![Image](https://github.com/user-attachments/assets/3e8286d3-265a-4a7f-ba8c-15ba1ad8eeaf)
claunia commented 2026-01-31 08:37:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Bah.

Okay, switching tactics a little bit. If you open up Event Viewer (eventvwr.msc), there may be an app reliability/crash entry for Terminal (WindowsTerminal.exe, wt.exe, OpenConsole.exe).

Can you grab the text from that?

@DHowett commented on GitHub (May 28, 2025): Bah. Okay, switching tactics a little bit. If you open up Event Viewer (`eventvwr.msc`), there may be an app reliability/crash entry for Terminal (WindowsTerminal.exe, wt.exe, OpenConsole.exe). Can you grab the text from that?
claunia commented 2026-01-31 08:37:16 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

None of those applications have entries in the Application section of the Windows Logs. I am using the Filter Current Log to specify the applications in the Event sources field. Not sure I am doing this correctly.

Ignore that! If I restrict the event log to Error and Critical the first Error I see is WindowTeminal.exe. Not sure how extract only the applications you asked for. Here is one error

Image

@RC51Owner commented on GitHub (May 28, 2025): None of those applications have entries in the Application section of the Windows Logs. I am using the Filter Current Log to specify the applications in the Event sources field. Not sure I am doing this correctly. Ignore that! If I restrict the event log to Error and Critical the first Error I see is WindowTeminal.exe. Not sure how extract only the applications you asked for. Here is one error ![Image](https://github.com/user-attachments/assets/d18a9805-7b34-4f19-b519-001f72596425)
claunia commented 2026-01-31 08:37:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Oh, that first entry is perfect! Can you grab everything out of the text box in General?

@DHowett commented on GitHub (May 28, 2025): Oh, that first entry is perfect! Can you grab everything out of the text box in General?
claunia commented 2026-01-31 08:37:16 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 28, 2025):

Here is the contents of the General Box:

Faulting application name: WindowsTerminal.exe, version: 1.22.2504.24001, time stamp: 0x680a8a16
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.26100.4061, time stamp: 0x23e9509f
Exception code: 0xc000027b
Fault offset: 0x0000000000903d93
Faulting process id: 0x79FC
Faulting application start time: 0x1DBD0150CFABEEA
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: a086d781-61fc-4c5f-9fca-097d7678cae4
Faulting package full name: Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Here is the information from the Details Pane (The reporting system didn't like the XML view so I am providing the Friendly View):

  • System

    • Provider

    [ Name] Application Error
    [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57}

    EventID 1000

    Version 0

    Level 2

    Task 100

    Opcode 0

    Keywords 0x8000000000000000

    • TimeCreated

    [ SystemTime] 2025-05-28T21:15:05.8924679Z

    EventRecordID 4514

    Correlation

    • Execution

    [ ProcessID] 6688
    [ ThreadID] 24756

    Channel Application

    Computer Perranporth

    • Security

    [ UserID] S-1-5-21-669574244-3257521472-950437955-1001

  • EventData

    AppName WindowsTerminal.exe
    AppVersion 1.22.2504.24001
    AppTimeStamp 680a8a16
    ModuleName Windows.UI.Xaml.dll
    ModuleVersion 10.0.26100.4061
    ModuleTimeStamp 23e9509f
    ExceptionCode c000027b
    FaultingOffset 0000000000903d93
    ProcessId 0x79fc
    ProcessCreationTime 0x1dbd0150cfabeea
    AppPath C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
    ModulePath C:\Windows\System32\Windows.UI.Xaml.dll
    IntegratorReportId a086d781-61fc-4c5f-9fca-097d7678cae4
    PackageFullName Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe
    PackageRelativeAppId App

@RC51Owner commented on GitHub (May 28, 2025): Here is the contents of the General Box: Faulting application name: WindowsTerminal.exe, version: 1.22.2504.24001, time stamp: 0x680a8a16 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.26100.4061, time stamp: 0x23e9509f Exception code: 0xc000027b Fault offset: 0x0000000000903d93 Faulting process id: 0x79FC Faulting application start time: 0x1DBD0150CFABEEA Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: a086d781-61fc-4c5f-9fca-097d7678cae4 Faulting package full name: Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Here is the information from the Details Pane (The reporting system didn't like the XML view so I am providing the Friendly View): - System - Provider [ Name] Application Error [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57} EventID 1000 Version 0 Level 2 Task 100 Opcode 0 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2025-05-28T21:15:05.8924679Z EventRecordID 4514 Correlation - Execution [ ProcessID] 6688 [ ThreadID] 24756 Channel Application Computer Perranporth - Security [ UserID] S-1-5-21-669574244-3257521472-950437955-1001 - EventData AppName WindowsTerminal.exe AppVersion 1.22.2504.24001 AppTimeStamp 680a8a16 ModuleName Windows.UI.Xaml.dll ModuleVersion 10.0.26100.4061 ModuleTimeStamp 23e9509f ExceptionCode c000027b FaultingOffset 0000000000903d93 ProcessId 0x79fc ProcessCreationTime 0x1dbd0150cfabeea AppPath C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe ModulePath C:\Windows\System32\Windows.UI.Xaml.dll IntegratorReportId a086d781-61fc-4c5f-9fca-097d7678cae4 PackageFullName Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe PackageRelativeAppId App
claunia commented 2026-01-31 08:37:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Internal debugging notes:
I was only able to find one signature (looked at ~20 CABs) that matched the version, exception code and fault offset.

Bucket: af916e62-580a-7f09-d2bf-2b1ce54c169d
Name: STOWED_EXCEPTION_XAML_TEXT_Not_enough_memory_resources_are_available_to_process_this_command_80070008_Windows.UI.Xaml.dll!CPopup::EnsureWindowForWindowedPopup

@DHowett commented on GitHub (May 28, 2025): Internal debugging notes: I was only able to find one signature (looked at ~20 CABs) that matched the version, exception code and fault offset. Bucket: af916e62-580a-7f09-d2bf-2b1ce54c169d Name: STOWED_EXCEPTION_XAML_TEXT_Not_enough_memory_resources_are_available_to_process_this_command_80070008_Windows.UI.Xaml.dll!CPopup::EnsureWindowForWindowedPopup
claunia commented 2026-01-31 08:37:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 29, 2025):

Alright, we're getting into increasingly unlikely debugging scenarios...

Can you run these from Command Prompt and report their output?

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" /v USERProcessHandleQuota
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" /v GdiProcessHandleQuota
@DHowett commented on GitHub (May 29, 2025): Alright, we're getting into increasingly unlikely debugging scenarios... Can you run these from Command Prompt and report their output? ``` reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" /v USERProcessHandleQuota reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows" /v GdiProcessHandleQuota ```
claunia commented 2026-01-31 08:37:17 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 29, 2025):

Image

@RC51Owner commented on GitHub (May 29, 2025): ![Image](https://github.com/user-attachments/assets/5f324748-6c8c-4c3d-bcd5-d87cf88b6093)
claunia commented 2026-01-31 08:37:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 29, 2025):

Drat. That's the expected values.

So, the crash is coming from deep inside the XAML (UI framework) "pop-up" window machinery. Probably it's trying to create a tooltip. Something in there is reporting that it's out of memory--or resources in general--and there is very little to go on apart from that. :/

@DHowett commented on GitHub (May 29, 2025): Drat. That's the expected values. So, the crash is coming from deep inside the XAML (UI framework) "pop-up" window machinery. Probably it's trying to create a tooltip. Something in there is reporting that it's out of memory--or resources in general--and there is very little to go on apart from that. :/
claunia commented 2026-01-31 08:37:19 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (May 29, 2025):

My machine has 32G of RAM (shared with the dGPU). It is a AMD RYZEN AI MAX+ 395+ w Radeon 8060S

@RC51Owner commented on GitHub (May 29, 2025): My machine has 32G of RAM (shared with the dGPU). It is a AMD RYZEN AI MAX+ 395+ w Radeon 8060S
claunia commented 2026-01-31 08:37:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 4, 2025):

Hey, are you by chance using the dropdown menu, the + button, or Ctrl+Shift+T to open your second tab?

This crash implicates the part of the Windows UI that generates tooltips specifically. Trying to narrow down exactly when we'd be creating one of those. 😁

@DHowett commented on GitHub (Jun 4, 2025): Hey, are you by chance using the dropdown menu, the `+` button, or <kbd>Ctrl+Shift+T</kbd> to open your second tab? This crash implicates the part of the Windows UI that generates tooltips specifically. Trying to narrow down exactly when we'd be creating one of those. 😁
claunia commented 2026-01-31 08:37:19 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (Jun 4, 2025):

Hey Dustin,

both the "+" and the drop-down menu options have been what I have tested that fail. I have not tried the Ctrl+Shift+T to open the second default tab,

@RC51Owner commented on GitHub (Jun 4, 2025): Hey Dustin, both the "+" and the drop-down menu options have been what I have tested that fail. I have not tried the Ctrl+Shift+T to open the second default tab,
claunia commented 2026-01-31 08:37:20 +00:00
Author
Owner
Copy Link

@RC51Owner commented on GitHub (Jun 4, 2025):

I just tried it and the "+" opens the second tab now. Likewise it also works when I choose the Ubuntu bash through the drop down menu. And Ctrl+Shift+T also works now as well....

@RC51Owner commented on GitHub (Jun 4, 2025): I just tried it and the "+" opens the second tab now. Likewise it also works when I choose the Ubuntu bash through the drop down menu. And Ctrl+Shift+T also works now as well....
claunia commented 2026-01-31 08:37:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 4, 2025):

Uuuuuhhhhh.. thanks! Let us know if it comes back! I'll reopen it then. 🙃

@DHowett commented on GitHub (Jun 4, 2025): Uuuuuhhhhh.. thanks! Let us know if it comes back! I'll reopen it then. 🙃
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 Needs-Attention Needs-Tag-Fix Needs-Triage 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#23264
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?