Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
HO-COOH opened this issue Jan 24, 2025 · 4 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Severity-Crash Crashes are real bad news.

Comments

@HO-COOH
Copy link
Contributor

HO-COOH commented Jan 24, 2025

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

@HO-COOH HO-COOH added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 24, 2025
Copy link

We've found some similar issues:

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.

@statchamber
Copy link

statchamber commented Jan 25, 2025

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

@Swaraj-SG
Copy link

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

@carlos-zamora carlos-zamora added Severity-Crash Crashes are real bad news. Product-Terminal The new Windows Terminal. labels Jan 29, 2025
@carlos-zamora carlos-zamora added this to the Terminal v1.24 milestone Jan 29, 2025
@carlos-zamora carlos-zamora removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jan 29, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Jan 29, 2025
@lanwin
Copy link

lanwin commented Jan 30, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Severity-Crash Crashes are real bad news.
Projects
None yet
Development

No branches or pull requests

5 participants