starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal hangs constantly while running WSL 2 #21556

New Issue
Open
opened 2026-01-31 07:48:05 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:48:05 +00:00
Owner
Copy Link

Originally created by @lumbytyci on GitHub (Apr 21, 2024).

Windows Terminal version

1.19.10821.0

Windows build number

10.0.22631.3447

Other Software

WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3447

Steps to reproduce

  1. Open Windows Terminal
  2. Launch WSL 2 (I'm running Debian)
  3. Do some work, usually happens after I save and quit from vim or any console application that has some kind of CLI
  4. Windows Terminal will hang (not freeze, there is no Program Not Responding message).

This will happen every few minutes or so. When this happens I have to wait ~30 seconds for the terminal to become responsive. Once responding, all of the previously buffered inputs will flush into the terminal.

Recently I discovered a way to immediately make the terminal responsive once it starts to hang. I do this by sending a SIGINT/Ctrl + C which immediately registers in the terminal (^C) and afterwards zooming in or out (ctrl +/-) - this seems to do the trick.

I'm directing this issue to this repository as opposed to the WSL repository since this issue is not reproducible with other terminal applications.
I can observe this identical issue in both of my devices running Windows 11.

Expected Behavior

Windows Terminal should not hang

Actual Behavior

Windows Terminal hangs

Originally created by @lumbytyci on GitHub (Apr 21, 2024). ### Windows Terminal version 1.19.10821.0 ### Windows build number 10.0.22631.3447 ### Other Software WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22631.3447 ### Steps to reproduce 1. Open Windows Terminal 2. Launch WSL 2 (I'm running Debian) 3. Do some work, usually happens after I save and quit from vim or any console application that has some kind of CLI 4. Windows Terminal will hang (not freeze, there is no Program Not Responding message). This will happen every few minutes or so. When this happens I have to wait ~30 seconds for the terminal to become responsive. Once responding, all of the previously buffered inputs will flush into the terminal. Recently I discovered a way to immediately make the terminal responsive once it starts to hang. I do this by sending a **SIGINT/Ctrl + C** which immediately registers in the terminal (^C) and afterwards zooming in or out (ctrl +/-) - this seems to do the trick. I'm directing this issue to this repository as opposed to the WSL repository since this issue is not reproducible with other terminal applications. I can observe this identical issue in both of my devices running Windows 11. ### Expected Behavior Windows Terminal should not hang ### Actual Behavior Windows Terminal hangs
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:48:05 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21556
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?