Windows Terminal Preview hangs and cannot close #18996

Closed
opened 2026-01-31 06:30:43 +00:00 by claunia · 6 comments
Owner

Originally created by @jerryc05 on GitHub (Dec 1, 2022).

Windows Terminal version

1.16.2642.0

Windows build number

10.0.22621.0

Other Software

WSL version: 1.0.0.0
Kernel version: 5.15.74.2

Steps to reproduce

  1. WSL "somehow" ran into a unresponsive state (e.g. huge amount of IO access)
  2. Run wsl --shutdown in the Windows "Run" program, trying to shutdown wsl
  3. The Windows Run program opens windows terminal by default to execute the command

Expected Behavior

No response

Actual Behavior

The popped up windows terminal hangs and cannot close. It does not even show the Profile tab on the top left corner

A minidump of this process is attached below (not sure if helpful)

WindowsTerminal.dmp.zip

Originally created by @jerryc05 on GitHub (Dec 1, 2022). ### Windows Terminal version 1.16.2642.0 ### Windows build number 10.0.22621.0 ### Other Software WSL version: 1.0.0.0 Kernel version: 5.15.74.2 ### Steps to reproduce 1. WSL "somehow" ran into a unresponsive state (e.g. huge amount of IO access) 2. Run `wsl --shutdown` in the Windows "Run" program, trying to shutdown wsl 3. The Windows Run program opens windows terminal by default to execute the command ### Expected Behavior _No response_ ### Actual Behavior The popped up windows terminal hangs and cannot close. It does not even show the Profile tab on the top left corner A minidump of this process is attached below (not sure if helpful) [WindowsTerminal.dmp.zip](https://github.com/microsoft/terminal/files/10129397/WindowsTerminal.dmp.zip)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:30:43 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Dec 2, 2022):

QQ, can you send a screenshot of the Terminal in this state? I bet there's a dupe sitting on the backlog, where the Terminal can't be closed if there are no tabs open. I reckon that's the situation you're in, and a screenshot would immediately identify that case.

@zadjii-msft commented on GitHub (Dec 2, 2022): QQ, can you send a screenshot of the Terminal in this state? I bet there's a dupe sitting on the backlog, where the Terminal can't be closed if there are _no_ tabs open. I reckon that's the situation you're in, and a screenshot would immediately identify that case.
Author
Owner

@jerryc05 commented on GitHub (Dec 2, 2022):

nope sorry I can't easily reproduce it. I just came across it and the best I can do is create a minidump and then force kill it

@jerryc05 commented on GitHub (Dec 2, 2022): nope sorry I can't easily reproduce it. I just came across it and the best I can do is create a minidump and then force kill it
Author
Owner

@zadjii-msft commented on GitHub (Dec 5, 2022):

Does it look anything like this:

image

From #12951

That's my guess, since all the threads in the dump seem to be in a fairly normal state, just waiting for any message from the OS.

@zadjii-msft commented on GitHub (Dec 5, 2022): Does it look anything like this: ![image](https://user-images.githubusercontent.com/18356694/205741655-2851b5ea-3d64-44e7-aa63-7741ba8de20f.png) From #12951 That's my guess, since all the threads in the dump seem to be in a fairly normal state, just waiting for any message from the OS.
Author
Owner

@jerryc05 commented on GitHub (Dec 5, 2022):

exactly the same!

@jerryc05 commented on GitHub (Dec 5, 2022): exactly the same!
Author
Owner

@zadjii-msft commented on GitHub (Dec 6, 2022):

You know, I'm gonna close this as a dupe then. Fixing that should fix whatever you were seeing. /dup #12951

@zadjii-msft commented on GitHub (Dec 6, 2022): You know, I'm gonna close this as a dupe then. Fixing that should fix whatever you were seeing. /dup #12951
Author
Owner

@ghost commented on GitHub (Dec 6, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Dec 6, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18996