-
Notifications
You must be signed in to change notification settings - Fork 8.7k
Open
Labels
Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting
Description
Windows Terminal version
1.22.12111.0
Windows build number
10.0.26100.0
Other Software
Any games (e.g., Limbus Company, Delta Force).
Steps to reproduce
- Launch Windows Terminal.
- Launch a game.
- Attempt to interact with the terminal's UI (e.g., by typing).
- Observe that the terminal's GUI is frozen.
Expected Behavior
The Windows Terminal should remain responsive and usable, even when a resource-intensive game is running in the background.
Actual Behavior
The terminal's GUI becomes unresponsive. Keystrokes are buffered but not rendered, and the UI does not
update. After a long, indeterminate period, the terminal might process the buffered commands all at once
before freezing again.
We have captured crash dumps during these periods of unresponsiveness and identified the following consistent exception details:
- Exception Code: 0x80000003 (A breakpoint was reached)
- Faulting Modules & Call Stacks:
* Scenario 1: Playing Delta Force
* Faulting Module: Win32u.dll
* Stack Trace: in32u!NtUserGetMessage
* Scenario 2: Playing Limbus Company
* Faulting Module: Win32u.dll
* Stack Trace: coreclr!Thread::DoAppropriateAptstateWait
Dump files are available upon request.
Metadata
Metadata
Assignees
Labels
Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting