Crash when closing one terminal window, all other terminal instances get killed

[HO-COOH]

Windows Terminal version

1.21.3231.0

Windows build number

22621.1413

Other Software

powershell 5.1

Steps to reproduce

I have several powershell instances, running in separate windows terminal instances. (So they should be separate processes) I closed one, it seems like it crashed. (powershell itself did not crash, I believe) All my other terminal instances get killed (including those running powershell), and I am toasted. 💢

Expected Behavior

No response

Actual Behavior

Dump too big to upload to github, so I submited a feedback with the dump. https://aka.ms/AAu35be

[similar-issues-ai[bot]]

We've found some similar issues:

• #11724 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[ghost]

same is happening but without running any powershell instances has happened so many times restarting wont help

[Swaraj-SG]

I was having the same issue but then i resetted my whole pc and now its gone !

[lanwin]

I have the same issue when debugging 3 terminal apps with Visual Studio. I am not sure yet, but when the debugger stops, all other Terminals are also gone.

Faulting application name: WindowsTerminal.exe, version: 1.21.2411.18001, time stamp: 0x673bd9f6
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.21.2411.18001, time stamp: 0x673bd875
Exception code: 0xc0000005
Fault offset: 0x000000000004b34f
Faulting process id: 0x632C
Faulting application start time: 0x1DB7310604B66A7
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.3231.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.3231.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: 192670ff-eeb1-496d-8560-276a1c777e3d
Faulting package full name: Microsoft.WindowsTerminal_1.21.3231.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[ppena-LiveData]

The same thing happens to me (with essentially an identical Windows Event as lanwin), but the whole Terminal process also sometimes crashes just when I put the computer to sleep and wake it up again.

[lanwin]

It seems its not related to the debugger. It happens in between and I can not see anything could be related to this. I have mostly three cmd processes running in the background and at some point Terminal disappears. When I remember correctly it does not happen when I work with Terminal. It only seems to happen when Terminal is in Background. For me I can exclude sleep since my pc is always on.

[mgua]

can it be that all the other terminal windows were started from the window that crashed?

[ppena-LiveData]

Sorry, I don't know about other people, but I only have a single Terminal window open with numerous tabs. It doesn't always crash, but sometimes when I close one of the tabs or put the computer to sleep, the whole Terminal crashes. Although, it hasn't happened in the past few days, so I'm not sure what's going on.

[HO-COOH]

can it be that all the other terminal windows were started from the window that crashed?

@mgua I don't think this matters (and I should have launched them separately). If it has parent-child relationship, closing the parent windows terminal process should also kill others even in normal circumstances, but it is not the case.

[igorehan]

I confirm the issue with v1.22.10352.0 (currently on Windows 11 26100.3194). I first noticed it on v1.21.2411.18001 (but may be earlier). I use Windows Terminal mainly for WSL. When exiting WSL (using Ctrl-D), the window freezes for 2 seconds, and then all instances of Windows Terminal are closed (no matter how many tabs I had in the Windows Terminal window and how many instances of these windows were open). This does not happen all the time, completely randomly (but several times a day). Each time it crashes, a report is created in the Application log, like in @lanwin case

[2-5]

Interestingly, all non-admin Windows Terminals were killed when one crashed, but the Administrator Windows Terminal instance survived.

[zdm]

Is it possible to do something with this? This is real problem, especially when some long running processes were launched in other terminal windows. It kills whole progress.

[sun2ot]

Encountered the same problem. When I switch Windows Terminal from the background to the foreground by clicking on the taskbar, there is a "unresponsive" situation. Then WT will completely freeze and kill all other instances.

[scottclark8]

Seeing the same problem; version 1.21.10351.0. I've got a test script (batch file) that runs for about 1 hour. During the test, the script fires off 48 new terminal sessions using start "title" cmd /S /C ... periodically. Each new terminal session does some stuff for about 30 - 60 seconds, then exits. Came in this morning, and all my terminal windows were gone! Event Viewer shows it / they crashed:

Faulting application name: WindowsTerminal.exe, version: 1.21.2502.4001, time stamp: 0x67a2980a Faulting module name: igd10um64gen11.DLL, version: 30.0.101.1660, time stamp: 0x6234f307 Exception code: 0xc0000005 Fault offset: 0x00000000000581e4 Faulting process id: 0x1138 Faulting application start time: 0x1DB87A4BEC41AA1 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_def655a57f98ffe7\igd10um64gen11.DLL Report Id: 3aa37348-2953-47a4-8096-86661ff284eb Faulting package full name: Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App

[vient]

Happened to me as well, when I closed WSL tab.

Faulting application name: WindowsTerminal.exe, version: 1.21.2502.4001, time stamp: 0x67a2980a
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.21.2502.4001, time stamp: 0x67a29682
Exception code: 0xc0000005
Fault offset: 0x000000000004b34f
Faulting process id: 0x4DAC
Faulting application start time: 0x1DB8C5EA66F0F7F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: 5e29d1c7-d7e4-4c58-9052-7dbd1b920e96
Faulting package full name: Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Offset is corresponding to this line, seems that _engines contains an invalid pointer and application crashes on this line when it tries to load pEngine's vtable.

---

@scottclark8 not sure your problem is the same one. Note that we have crash in Microsoft.Terminal.Control.dll while you have it in igd10um64gen11.DLL, which seems to be an Intel Graphics driver dll.

[mpdunlop]

Encountering exactly the same issue as @lanwin described where closing one Visual Studio debugger instances causes Windows Terminal to crash, closing all unrelated cmd and wsl tabs. it's very annoying when dependencies in other tabs are mysteriously closed!

Faulting application name: WindowsTerminal.exe, version: 1.22.2502.4002, time stamp: 0x67a29904
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.22.2502.4002, time stamp: 0x67a29778
Exception code: 0xc0000005
Fault offset: 0x0000000000040a3f
Faulting process id: 0x1183C
Faulting application start time: 0x1DB92F2F17A6262
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.10352.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.10352.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: f94f0db0-2aa4-4849-a91c-864643c32aca
Faulting package full name: Microsoft.WindowsTerminal_1.22.10352.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[tygh89071388]

I have two computers, one with an AMD 9950X and one with an Intel 13900K. Both have experienced the same problem.

失敗的應用程式名稱： WindowsTerminal.exe，版本： 1.21.2502.4001，時間戳記： 0x67a2980a
錯誤模組名稱： Windows.UI.Xaml.dll， 版本： 10.0.26100.2894，時間戳記： 0xc544c6f0
例外狀況代碼： 0xc0000005
錯誤位移： 0x00000000005152af
錯誤處理常式識別碼： 0x2368
失敗的應用程式開始時間： 0x1DB8BB0F85C39DF
Faulting 應用程式路徑： C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting 模組路徑： C:\Windows\System32\Windows.UI.Xaml.dll
Report 識別碼： 52c56554-2c9d-4f56-8b07-5752fb7bf42e
Faulting 套件完整名稱： Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe
Faulting 套件相對應用程式識別碼： App

-----------------

錯誤容器 2190415804041462436，類型 5
事件名稱: MoAppCrash
回應: 無法使用
Cab 識別碼: 0

問題簽章:
P1: Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.21.2502.4001
P4: 67a2980a
P5: Windows.UI.Xaml.dll
P6: 10.0.26100.3323
P7: 486e0ba2
P8: c0000005
P9: 000000000051316f
P10: 

附加檔案:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.de7872fd-b53e-434f-8d3c-0960c5a1340f.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.95272dfc-ccb0-41ec-9811-7cb18b0e0b44.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.dbf2c1b6-22c7-4cc5-95df-151e21bb41c1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0e93298a-3a47-491a-bd9f-e39bd645b0ed.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1f371c7d-dcff-4f1e-8785-2082d3c164ba.tmp.xml

這些檔案可能在這裡:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_eaae6565e15312e5141c3f4f849c8056715859_abde1418_e2c0de8f-c003-4972-8895-3fe2afea8157

分析符號: 
重新檢查解決方案: 0
報告識別碼: 68bbcfb1-f8ae-47d7-9e47-c3e92754214a
報告狀態: 268435456
雜湊化容器: e330f124a8bfdc5bce65eb91864b02a4
Cab GUID: 0

[Report.zip](https://github.com/user-attachments/files/19206084/Report.zip)

[scottclark8]

Happened to me as well, when I closed WSL tab.

Faulting application name: WindowsTerminal.exe, version: 1.21.2502.4001, time stamp: 0x67a2980a
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.21.2502.4001, time stamp: 0x67a29682
Exception code: 0xc0000005
Fault offset: 0x000000000004b34f
Faulting process id: 0x4DAC
Faulting application start time: 0x1DB8C5EA66F0F7F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: 5e29d1c7-d7e4-4c58-9052-7dbd1b920e96
Faulting package full name: Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Offset is corresponding to this line, seems that _engines contains an invalid pointer and application crashes on this line when it tries to load pEngine's vtable.

@scottclark8 not sure your problem is the same one. Note that we have crash in Microsoft.Terminal.Control.dll while you have it in igd10um64gen11.DLL, which seems to be an Intel Graphics driver dll.

Agreed, my faulting app is different, but the behavior is the same; i.e. opening and closing a bunch of terminals can cause a crash, resulting in all terminal windows closing, which for me is the problem. Interestingly I'm doing this behavior pretty much every day, and I've only seen this specific problem twice in the last 6 or so months.

[lanwin]

Maybe #18620 is realted to that?

[mgua]

I am sorry I can not provide steps for reproduction.

I have a pwsh script launching several ms terminal windows, and running local tasks in each. These tasks are python processes. A single pwsh script spawns all the windows. Each window is a ms terminal, single tab running a basic console application. The pwsh launcher is a shell enriched with ohmyposh, and uses nerdfonts. I typically perform manual git tasks and python launches inside these interfaces. I use CTRL+mousewheel quite a lot to zoom/in/out. While I have the WSL installed, i am not using it. In my case bug hits while running pure windows powershell and powershell launched tasks.

Sometimes when i actively close one of those windows using the x in the top right corner, after stopping with CTRL-C the process in it it, all the other open MS terminal windows are closed, and their processes killed. the kill is istantaneous, and all the windows are simultaneously closed at once. No errors are shown. I did not find a way to reproduce it.

In all the windows i run powershell, which is activating python 3.12 venvs, and then python scripts are launched. I do not think the bug depends from whatever the python code is sending to the stdout. I have two identical windows 11 machines, and I experienced the bug in both. I normally access those machines via rdp using mstsc from my windows desktop machine.

The bug occurrence is quite rare (maybe once every 12-15 days or so).

[salo-dea]

For me this happens almost every day when I close various tabs at the end of a work day.

I tried the latest Preview version, as mentioned by @lanwin, but (atleast for me) it seems not fixed yet

Faulting application name: WindowsTerminal.exe, version: 1.23.2503.14002, time stamp: 0x67d4a928
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.23.2503.14002, time stamp: 0x67d4a78f
Exception code: 0xc0000005
Fault offset: 0x0000000000041c90
Faulting process id: 0x5FF0
Faulting application start time: 0x1DB98A574C875A7
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.23.10732.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.23.10732.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: d60e451a-91cc-4a47-8ecb-9d8397761592
Faulting package full name: Microsoft.WindowsTerminalPreview_1.23.10732.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[DHowett]

Alright, so! Looking at all these dumps and the teardown process, we took a beat and reworked how shutting down individual controls (read: terminals, either in split panes or tabs) works in #18632.

Unfortunately, we weren't able to reproduce the original issue in Preview or Stable. I tried running something with a lot of output (guaranteed to cause contention on the output->renderer pipeline at least) in multiple windows while I closed them.

Given that some of you all have better repros than we do: #18632 is out in the Canary channel right now. Would you be able to validate it? It runs side by side with Preview, so shouldn't interfere with your existing settings.

[salo-dea]

I've been using the Canary version since March 20th and so far I haven't had a single crash. Maybe it's not enough time to tell but atleast for now I'm not afraid about quickly closing all my open tabs/panes anymore😄.

[2-5]

In case this helps, the crash reports from above that I checked crashed with Exception code: 0xc0000005, but Terminal crashed for me today when closing a window with Exception code: 0xc0000374 which is STATUS_HEAP_CORRUPTION:

Faulting application name: WindowsTerminal.exe, version: 1.22.2503.14001, time stamp: 0x67d4a8f9
Faulting module name: ntdll.dll, version: 10.0.22621.5124, time stamp: 0x82bfa2b9
Exception code: 0xc0000374
Fault offset: 0x000000000010cbb9
Faulting process id: 0x0x3C14
Faulting application start time: 0x0x1DB9FB4D4BDD8E1
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.10731.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e90db9de-322c-47f5-9408-05fa4381325a
Faulting package full name: Microsoft.WindowsTerminal_1.22.10731.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[chdh]

I have frequent crashes of this type since the upgrade to the current Terminal version 1.22.11141.0. It crashes about twice a day. But in my case the fault seems to be in Windows.UI.Xaml.dll.

Faulting application name: WindowsTerminal.exe, version: 1.22.2504.24001, time stamp: 0x680a8a16
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.26100.3775, time stamp: 0xafe9f314
Exception code: 0xc0000005
Fault offset: 0x000000000051388f
Faulting process id: 0x2F14
Faulting application start time: 0x1DBBF4CFF2EBAF0
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: b1fc8fec-acfb-415b-85cb-a77284303b7d
Faulting package full name: Microsoft.WindowsTerminal_1.22.11141.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

[lanwin]

For me the crashes seems to be gone since the lastest updated.

[saumitra91]

Similar issue here. While working with multiple terminal windows, if one crashes/ freezes on closing, all the other terminal windows close. Please fix this!

[Jan98989]

Same problem on last version 1.23. If you open 5+ terminals with 5 tabs in, and start close terminal fast, your all other terminals crash.