reattaching a tab unexpectedly closes windows terminal #22967

Closed
opened 2026-01-31 08:28:42 +00:00 by claunia · 5 comments
Owner

Originally created by @jstnfst on GitHub (Feb 22, 2025).

Windows Terminal version

No response

Windows build number

Version: 1.21.10351.0

Other Software

No response

Steps to reproduce

  1. use a vpn
  2. open several tabs in Windows Terminal using powershell
  3. open several ssh sessions from each tab; cat lots of files; build lots of projects; use lots of tools...
  4. continue working for several hours; all is as normal; these terminal sessions will have lots of text
  5. tear a tab off of windows terminal; this creates a new window with my ssh session, and all is well
  6. reattach the torn off tab to the previous window that it came from
  7. crash; all tabs disappear; all work is lost; Windows Terminal o7 bye

Expected Behavior

reattaching a tab should work and not crash

Actual Behavior

it crashed like this twice, which is why i'm spending the time to write this up

Originally created by @jstnfst on GitHub (Feb 22, 2025). ### Windows Terminal version _No response_ ### Windows build number Version: 1.21.10351.0 ### Other Software _No response_ ### Steps to reproduce 1. use a vpn 2. open several tabs in Windows Terminal using powershell 3. open several ssh sessions from each tab; cat lots of files; build lots of projects; use lots of tools... 4. continue working for several hours; all is as normal; these terminal sessions will have lots of text 5. tear a tab off of windows terminal; this creates a new window with my ssh session, and all is well 6. reattach the torn off tab to the previous window that it came from 7. crash; all tabs disappear; all work is lost; Windows Terminal o7 bye ### Expected Behavior reattaching a tab should work and not crash ### Actual Behavior it crashed like this twice, which is why i'm spending the time to write this up
claunia added the Needs-TriageIssue-BugNeeds-Author-Feedback labels 2026-01-31 08:28:42 +00:00
Author
Owner

@lhecker commented on GitHub (Feb 26, 2025):

To be honest, unfortunately repro steps like this are not very helpful. We don't have access to your VPN, don't have your ssh details, don't know what files to cat, nor in what exact order and fashion you tore the tabs off in order to reproduce this.

Instead, please consider capturing crash dumps when an application is crashing. This doesn't just apply to Windows Terminal, but actually any application (on any operating system). For Windows Terminal in particular, you can follow these steps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

I suspect your issue will be fixed by #18632, which is our largest crash source right now and happens when reattaching tabs (among others). If you'd like to further investigate this, please capture a crash dump as mentioned above and send it to us (<my github username>@microsoft.com). But I'm like 90% sure it's fixed by #18632. 🙂

@lhecker commented on GitHub (Feb 26, 2025): To be honest, unfortunately repro steps like this are not very helpful. We don't have access to your VPN, don't have your ssh details, don't know what files to cat, nor in what exact order and fashion you tore the tabs off in order to reproduce this. Instead, please consider capturing crash dumps when an application is crashing. This doesn't just apply to Windows Terminal, but actually any application (on any operating system). For Windows Terminal in particular, you can follow these steps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically I suspect your issue will be fixed by #18632, which is our largest crash source right now and happens when reattaching tabs (among others). If you'd like to further investigate this, please capture a crash dump as mentioned above and send it to us (`<my github username>@microsoft.com`). But I'm like 90% sure it's fixed by #18632. 🙂
Author
Owner

@ClaireCJS commented on GitHub (Jun 2, 2025):

Well un-mark it as stale. This is a horrible experience and the cumulative work i lose due to this bug has reached hours.

@ClaireCJS commented on GitHub (Jun 2, 2025): Well un-mark it as stale. This is a horrible experience and the cumulative work i lose due to this bug has reached hours.
Author
Owner

@ClaireCJS commented on GitHub (Jun 2, 2025):

Window re-attachment with Windows Terminal is so unreliable that nowadays, if a window detaches, I try to finish up the job in that window and just do all the steps required to re-start it in another window, because re-attachment THREATENS EVERY PROCESS and I’m usually running at least 20 tabs running at least 20 scripts...

It’s HORRIBLE. Please put somebody on it. I don’t know why it’s hard to reproduce. Maybe you don’t have enough in your scrollback bufffers.

@ClaireCJS commented on GitHub (Jun 2, 2025): Window re-attachment with Windows Terminal is so unreliable that nowadays, if a window detaches, I try to finish up the job in that window and just do all the steps required to re-start it in another window, because re-attachment THREATENS EVERY PROCESS and I’m usually running at least 20 tabs running at least 20 scripts... It’s HORRIBLE. Please put somebody on it. I don’t know why it’s hard to reproduce. Maybe you don’t have enough in your scrollback bufffers.
Author
Owner

@ClaireCJS commented on GitHub (Jun 2, 2025):

To be honest, unfortunately repro steps like this are not very helpful. We don't have access to your VPN, don't have your ssh details, don't know what files to cat, nor in what exact order and fashion you tore the tabs off in order to reproduce this.

Instead, please consider capturing crash dumps when an application is crashing. This doesn't just apply to Windows Terminal, but actually any application (on any operating system). For Windows Terminal in particular, you can follow these steps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

I suspect your issue will be fixed by #18632, which is our largest crash source right now and happens when reattaching tabs (among others). If you'd like to further investigate this, please capture a crash dump as mentioned above and send it to us (<my github username>@microsoft.com). But I'm like 90% sure it's fixed by #18632. 🙂

that PR looks closed and this issue persists

@ClaireCJS commented on GitHub (Jun 2, 2025): > To be honest, unfortunately repro steps like this are not very helpful. We don't have access to your VPN, don't have your ssh details, don't know what files to cat, nor in what exact order and fashion you tore the tabs off in order to reproduce this. > > Instead, please consider capturing crash dumps when an application is crashing. This doesn't just apply to Windows Terminal, but actually any application (on any operating system). For Windows Terminal in particular, you can follow these steps: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically > > I suspect your issue will be fixed by [#18632](https://github.com/microsoft/terminal/pull/18632), which is our largest crash source right now and happens when reattaching tabs (among others). If you'd like to further investigate this, please capture a crash dump as mentioned above and send it to us (`<my github username>@microsoft.com`). But I'm like 90% sure it's fixed by [#18632](https://github.com/microsoft/terminal/pull/18632). 🙂 that PR looks closed and this issue persists
Author
Owner

@lhecker commented on GitHub (Jun 2, 2025):

Do you have a crash dump that you could share with us?

@lhecker commented on GitHub (Jun 2, 2025): Do you have a crash dump that you could share with us?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22967