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

Exiting a tab sometimes closes the entire window #14074

New Issue
Closed
opened 2026-01-31 04:00:10 +00:00 by claunia · 15 comments
claunia commented 2026-01-31 04:00:10 +00:00
Owner
Copy Link

Originally created by @quanticle on GitHub (May 31, 2021).

Windows Terminal version (or Windows build number)

1.8.1444.0

Other Software

  • GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) (in WSL)
  • Windows PowerShell 7.1.3

Steps to reproduce

This is a very intermittent bug, but the consequences are rather catastrophic when the bug does occur. Very rarely, when I type exit inside either a WSL bash session or in PowerShell, the entire Windows Terminal window exits, rather than just individual tab.

Expected Behavior

I would expect just the individual tab to close when I exit a WSL bash or Windows PowerShell session.

Actual Behavior

All tabs close, terminating other terminals that have long-running jobs in them.

Originally created by @quanticle on GitHub (May 31, 2021). ### Windows Terminal version (or Windows build number) 1.8.1444.0 ### Other Software - GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) (in WSL) - Windows PowerShell 7.1.3 ### Steps to reproduce This is a very intermittent bug, but the consequences are rather catastrophic when the bug does occur. Very rarely, when I type `exit` inside either a WSL bash session or in PowerShell, the entire Windows Terminal window exits, rather than just individual tab. ### Expected Behavior I would expect just the individual tab to close when I exit a WSL bash or Windows PowerShell session. ### Actual Behavior All tabs close, terminating other terminals that have long-running jobs in them.
claunia commented 2026-01-31 04:00:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 1, 2021):

Interesting. I thought we had gotten all the crash-on-exits worked out in the last release, so it worries me that another is hiding.

I know you mention that this happens intermittently, but the best way for us to investigate this is to get the crash repro'd with the Feedback Hub:

/feedback

That'll get us a stack trace we can use to actually try and root-cause this

@zadjii-msft commented on GitHub (Jun 1, 2021): Interesting. I thought we had gotten all the crash-on-exits worked out in the last release, so it worries me that another is hiding. I know you mention that this happens intermittently, but the best way for us to investigate this is to get the crash repro'd with the Feedback Hub: /feedback That'll get us a stack trace we can use to actually try and root-cause this
claunia commented 2026-01-31 04:00:13 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 1, 2021):

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 (Jun 1, 2021): 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 04:00:13 +00:00
Author
Owner
Copy Link

@hameno commented on GitHub (Jun 2, 2021):

I'm having the same problem since a few days. Very often the whole Terminal crashes.
I have found the following errors in event viewer:

Protokollname: Application
Quelle:        Application Error
Datum:         02.06.2021 17:14:45
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      XXX
Beschreibung:
Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94
Name des fehlerhaften Moduls: Microsoft.Terminal.Control.dll, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2c08
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000031113
ID des fehlerhaften Prozesses: 0x8d04
Startzeit der fehlerhaften Anwendung: 0x01d757b929938aa7
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Berichtskennung: 6db40d2b-154f-4f9e-9b97-0807c19cc3a6
Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-06-02T15:14:45.8124552Z" />
    <EventRecordID>1500853</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>XXX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>WindowsTerminal.exe</Data>
    <Data>1.8.2105.24004</Data>
    <Data>60ac2e94</Data>
    <Data>Microsoft.Terminal.Control.dll</Data>
    <Data>1.8.2105.24004</Data>
    <Data>60ac2c08</Data>
    <Data>c0000005</Data>
    <Data>0000000000031113</Data>
    <Data>8d04</Data>
    <Data>01d757b929938aa7</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll</Data>
    <Data>6db40d2b-154f-4f9e-9b97-0807c19cc3a6</Data>
    <Data>Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

Protokollname: Application
Quelle:        Application Error
Datum:         02.06.2021 16:09:59
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      XXX
Beschreibung:
Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94
Name des fehlerhaften Moduls: Microsoft.Terminal.Control.dll, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2c08
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000031113
ID des fehlerhaften Prozesses: 0x34e0
Startzeit der fehlerhaften Anwendung: 0x01d7577dbd60ebb4
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Berichtskennung: 08bef7c3-4006-4f4d-9b3e-9ef5e6d9cb2f
Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-06-02T14:09:59.0136117Z" />
    <EventRecordID>1500851</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>XXX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>WindowsTerminal.exe</Data>
    <Data>1.8.2105.24004</Data>
    <Data>60ac2e94</Data>
    <Data>Microsoft.Terminal.Control.dll</Data>
    <Data>1.8.2105.24004</Data>
    <Data>60ac2c08</Data>
    <Data>c0000005</Data>
    <Data>0000000000031113</Data>
    <Data>34e0</Data>
    <Data>01d7577dbd60ebb4</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll</Data>
    <Data>08bef7c3-4006-4f4d-9b3e-9ef5e6d9cb2f</Data>
    <Data>Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>
@hameno commented on GitHub (Jun 2, 2021): I'm having the same problem since a few days. Very often the whole Terminal crashes. I have found the following errors in event viewer: ``` Protokollname: Application Quelle: Application Error Datum: 02.06.2021 17:14:45 Ereignis-ID: 1000 Aufgabenkategorie:(100) Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: XXX Beschreibung: Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94 Name des fehlerhaften Moduls: Microsoft.Terminal.Control.dll, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2c08 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000031113 ID des fehlerhaften Prozesses: 0x8d04 Startzeit der fehlerhaften Anwendung: 0x01d757b929938aa7 Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Berichtskennung: 6db40d2b-154f-4f9e-9b97-0807c19cc3a6 Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2021-06-02T15:14:45.8124552Z" /> <EventRecordID>1500853</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>XXX</Computer> <Security /> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.8.2105.24004</Data> <Data>60ac2e94</Data> <Data>Microsoft.Terminal.Control.dll</Data> <Data>1.8.2105.24004</Data> <Data>60ac2c08</Data> <Data>c0000005</Data> <Data>0000000000031113</Data> <Data>8d04</Data> <Data>01d757b929938aa7</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll</Data> <Data>6db40d2b-154f-4f9e-9b97-0807c19cc3a6</Data> <Data>Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ``` ``` Protokollname: Application Quelle: Application Error Datum: 02.06.2021 16:09:59 Ereignis-ID: 1000 Aufgabenkategorie:(100) Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: XXX Beschreibung: Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94 Name des fehlerhaften Moduls: Microsoft.Terminal.Control.dll, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2c08 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000031113 ID des fehlerhaften Prozesses: 0x34e0 Startzeit der fehlerhaften Anwendung: 0x01d7577dbd60ebb4 Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Berichtskennung: 08bef7c3-4006-4f4d-9b3e-9ef5e6d9cb2f Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2021-06-02T14:09:59.0136117Z" /> <EventRecordID>1500851</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>XXX</Computer> <Security /> </System> <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.8.2105.24004</Data> <Data>60ac2e94</Data> <Data>Microsoft.Terminal.Control.dll</Data> <Data>1.8.2105.24004</Data> <Data>60ac2c08</Data> <Data>c0000005</Data> <Data>0000000000031113</Data> <Data>34e0</Data> <Data>01d7577dbd60ebb4</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll</Data> <Data>08bef7c3-4006-4f4d-9b3e-9ef5e6d9cb2f</Data> <Data>Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ```
claunia commented 2026-01-31 04:00:13 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 6, 2021):

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 (Jun 6, 2021): 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 04:00:13 +00:00
Author
Owner
Copy Link

@alefteris commented on GitHub (Jun 7, 2021):

I'm having this issue also after my upgrade from 1.7 to 1.8. I also upgraded to the 1.8.1521.0 that is supposed to fix various crashing issues, but it hasn't fixed this one. A workaround is to set in profile settings "closeOnExit": "never" . Unfortunately I can't submit feedback from the machine I'm using.

@alefteris commented on GitHub (Jun 7, 2021): I'm having this issue also after my upgrade from 1.7 to 1.8. I also upgraded to the 1.8.1521.0 that is supposed to fix various crashing issues, but it hasn't fixed this one. A workaround is to set in profile settings `"closeOnExit": "never"` . Unfortunately I can't submit feedback from the machine I'm using.
claunia commented 2026-01-31 04:00:14 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 7, 2021):

Can you send a screenshot next time it happens, with closeOnExit set to never? I suspect that you'll see a process exit code.

@DHowett commented on GitHub (Jun 7, 2021): Can you send a screenshot next time it happens, with `closeOnExit` set to `never`? I suspect that you'll see a process exit code.
claunia commented 2026-01-31 04:00:15 +00:00
Author
Owner
Copy Link

@pkropachev commented on GitHub (Jun 10, 2021):

I have the same problem during exit or hitting ctrl+d in one of the opened tabs with WSL.

Faulting application name: WindowsTerminal.exe, version: 1.8.2106.1001, time stamp: 0x60b64ad3
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.8.2106.1001, time stamp: 0x60b6485c
Exception code: 0xc0000005
Fault offset: 0x0000000000031103
Faulting process id: 0x3110
Faulting application start time: 0x01d75d333ee497cf
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: b0ab7ebe-b291-42aa-b2f6-72294e2ee44b
Faulting package full name: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
@pkropachev commented on GitHub (Jun 10, 2021): I have the same problem during `exit` or hitting `ctrl+d` in one of the opened tabs with WSL. ``` Faulting application name: WindowsTerminal.exe, version: 1.8.2106.1001, time stamp: 0x60b64ad3 Faulting module name: Microsoft.Terminal.Control.dll, version: 1.8.2106.1001, time stamp: 0x60b6485c Exception code: 0xc0000005 Fault offset: 0x0000000000031103 Faulting process id: 0x3110 Faulting application start time: 0x01d75d333ee497cf Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Report Id: b0ab7ebe-b291-42aa-b2f6-72294e2ee44b Faulting package full name: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia commented 2026-01-31 04:00:15 +00:00
Author
Owner
Copy Link

@SpitFire-666 commented on GitHub (Jun 12, 2021):

I just had a similar/same crash as some of the other guys, I think I was playing with the font setting when it spat the dummy for me:


Faulting application name: WindowsTerminal.exe, version: 1.9.2106.1003, time stamp: 0x60b67332
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.9.2106.1003, time stamp: 0x60b670d0
Exception code: 0xc0000005
Fault offset: 0x000000000000eb41
Faulting process id: 0x2a58
Faulting application start time: 0x01d75e8c594796ab
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.9.1523.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.9.1523.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: c4bb0fbe-89d6-4b15-8b63-6be08f5b3d8f
Faulting package full name: Microsoft.WindowsTerminalPreview_1.9.1523.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
@SpitFire-666 commented on GitHub (Jun 12, 2021): I just had a similar/same crash as some of the other guys, I think I was playing with the font setting when it spat the dummy for me: ``` Faulting application name: WindowsTerminal.exe, version: 1.9.2106.1003, time stamp: 0x60b67332 Faulting module name: Microsoft.Terminal.Control.dll, version: 1.9.2106.1003, time stamp: 0x60b670d0 Exception code: 0xc0000005 Fault offset: 0x000000000000eb41 Faulting process id: 0x2a58 Faulting application start time: 0x01d75e8c594796ab Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.9.1523.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.9.1523.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Report Id: c4bb0fbe-89d6-4b15-8b63-6be08f5b3d8f Faulting package full name: Microsoft.WindowsTerminalPreview_1.9.1523.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia commented 2026-01-31 04:00:16 +00:00
Author
Owner
Copy Link

@ManelyDave commented on GitHub (Jun 14, 2021):

Same thing here- super frustrating. I'm using the normal release to do production work and I keep losing my work happening in running scripts or command line test runs because of this error. I'm actually evaluating going back to other terminal emulators because I can't be slowed down like this, even though the other options are less performant than I'd like.

Faulting application name: WindowsTerminal.exe, version: 1.8.2106.1001, time stamp: 0x60b64ad3
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.8.2106.1001, time stamp: 0x60b6485c
Exception code: 0xc0000005
Fault offset: 0x0000000000022cd0
Faulting process id: 0x4c5c
Faulting application start time: 0x01d761224b7c8e37
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: 3b7db01d-dee9-4050-bf48-0619225e4674
Faulting package full name: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

@ManelyDave commented on GitHub (Jun 14, 2021): Same thing here- super frustrating. I'm using the normal release to do production work and I keep losing my work happening in running scripts or command line test runs because of this error. I'm actually evaluating going back to other terminal emulators because I can't be slowed down like this, even though the other options are less performant than I'd like. Faulting application name: WindowsTerminal.exe, version: 1.8.2106.1001, time stamp: 0x60b64ad3 Faulting module name: Microsoft.Terminal.Control.dll, version: 1.8.2106.1001, time stamp: 0x60b6485c Exception code: 0xc0000005 Fault offset: 0x0000000000022cd0 Faulting process id: 0x4c5c Faulting application start time: 0x01d761224b7c8e37 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Report Id: 3b7db01d-dee9-4050-bf48-0619225e4674 Faulting package full name: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
claunia commented 2026-01-31 04:00:16 +00:00
Author
Owner
Copy Link

@quanticle commented on GitHub (Jun 15, 2021):

I've been trying to reproduce the bug, and in the past three days, I've only managed to get it to repro once. In both instances the crash occurred after I exited Mosh.

@quanticle commented on GitHub (Jun 15, 2021): I've been trying to reproduce the bug, and in the past three days, I've only managed to get it to repro once. In both instances the crash occurred after I exited [Mosh](https://mosh.org/).
claunia commented 2026-01-31 04:00:16 +00:00
Author
Owner
Copy Link

@ManelyDave commented on GitHub (Jun 15, 2021):

When it happens for me, I'm in a bash shell within the WSL ubuntu instance and I've often just exited an SSH session to a remote server.

@ManelyDave commented on GitHub (Jun 15, 2021): When it happens for me, I'm in a bash shell within the WSL ubuntu instance and I've often just exited an SSH session to a remote server.
claunia commented 2026-01-31 04:00:17 +00:00
Author
Owner
Copy Link

@hameno commented on GitHub (Jun 15, 2021):

When it happens for me, I'm in a bash shell within the WSL ubuntu instance and I've often just exited an SSH session to a remote server.

Same here.

@hameno commented on GitHub (Jun 15, 2021): > When it happens for me, I'm in a bash shell within the WSL ubuntu instance and I've often just exited an SSH session to a remote server. Same here.
claunia commented 2026-01-31 04:00:17 +00:00
Author
Owner
Copy Link

@cg2v commented on GitHub (Jul 1, 2021):

I can't seem to find my feedback id, but the sharing url is https://aka.ms/AAd2dyk

@cg2v commented on GitHub (Jul 1, 2021): I can't seem to find my feedback id, but the sharing url is https://aka.ms/AAd2dyk
claunia commented 2026-01-31 04:00:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2021):

:tada:This issue was addressed in #10549, which has now been successfully released as Windows Terminal v1.9.1942.0.🎉

Handy links:

@ghost commented on GitHub (Jul 14, 2021): :tada:This issue was addressed in #10549, which has now been successfully released as `Windows Terminal v1.9.1942.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.9.1942.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 04:00:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2021):

:tada:This issue was addressed in #10549, which has now been successfully released as Windows Terminal Preview v1.10.1933.0.🎉

Handy links:

@ghost commented on GitHub (Jul 14, 2021): :tada:This issue was addressed in #10549, which has now been successfully released as `Windows Terminal Preview v1.10.1933.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.10.1933.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-Attention Needs-Tag-Fix Needs-Triage Product-Terminal Resolution-Fix-Committed 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#14074
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?