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

Windows Terminal deadlock/lockleak after startup. #18634

Open
YexuanXiao opened this issue Feb 27, 2025 · 2 comments
Open

Windows Terminal deadlock/lockleak after startup. #18634

YexuanXiao opened this issue Feb 27, 2025 · 2 comments
Labels
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

Comments

@YexuanXiao
Copy link
Contributor

YexuanXiao commented Feb 27, 2025

Windows Terminal version

1.23.10353

Windows build number

27788

Steps to reproduce

My computer pops up a Windows Terminal window upon startup, which becomes unresponsive and freezes. This has happened twice now, with the previous occurrence happening a few days ago. I attached to the process in VS, paused the program to check where it was blocked, and found that a lock is waiting and has never been notified within TerminalConnection.dll.

Image

Image

Image

@YexuanXiao YexuanXiao 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 Feb 27, 2025
@shaymuiruri

This comment has been minimized.

@microsoft microsoft deleted a comment from ket395 Feb 27, 2025
@YexuanXiao YexuanXiao changed the title Windows Terminal deadlock after startup. Windows Terminal deadlock/lockleak after startup. Mar 1, 2025
@GOATS2K
Copy link

GOATS2K commented Mar 4, 2025

I can confirm this is also happening for me on Windows 11 24H2, on version 1.21.10351.0 - with the exact same call stack according to x64dbg. It also happened to unfreeze itself after I closed a game that was open, possibly related to #18040.

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-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

3 participants