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

Windows terminal can get stuck completely and ignore any input #19318

New Issue
Closed
opened 2026-01-31 06:39:58 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:39:58 +00:00
Owner
Copy Link

Originally created by @lesleyrs on GitHub (Feb 6, 2023).

Windows Terminal version

1.15.3465.0

Windows build number

10.0.19045.0

Other Software

WSL

Steps to reproduce

I have reproduced this before but it doesn't seem that easy to do.

Sometimes when making a typo, then quickly retyping and hitting enter, windows terminal will no longer take any input unless you close the session and open a new one. It will accept ctrl-C once or twice which will make the cursor jump to start of the current line on top of your name as seen in the screenshot below. Then it ignores all input again.

Expected Behavior

I expected that it would not get stuck and continue to take input regardless of how quickly I'm using commands.

Actual Behavior

image

I just realised this screenshot only shows 1 typo, but I made 2. The second one causing the terminal to get stuck.

Haven't had this happen outside of WSL yet.

Not sure if this belongs here or at https://github.com/microsoft/WSL

Originally created by @lesleyrs on GitHub (Feb 6, 2023). ### Windows Terminal version 1.15.3465.0 ### Windows build number 10.0.19045.0 ### Other Software WSL ### Steps to reproduce I have reproduced this before but it doesn't seem that easy to do. Sometimes when making a typo, then quickly retyping and hitting enter, windows terminal will no longer take any input unless you close the session and open a new one. It will accept ctrl-C once or twice which will make the cursor jump to start of the current line on top of your name as seen in the screenshot below. Then it ignores all input again. ### Expected Behavior I expected that it would not get stuck and continue to take input regardless of how quickly I'm using commands. ### Actual Behavior ![image](https://user-images.githubusercontent.com/19632758/216858864-ef6fea04-5d42-4ce0-b1e1-c01152e57cfc.png) I just realised this screenshot only shows 1 typo, but I made 2. The second one causing the terminal to get stuck. Haven't had this happen outside of WSL yet. Not sure if this belongs here or at https://github.com/microsoft/WSL
claunia added the Issue-QuestionNeeds-TriageResolution-Answered labels 2026-01-31 06:39:59 +00:00
claunia commented 2026-01-31 06:40:00 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 6, 2023):

Hmm... Unfortunately for us to debug this, we'd first need a consistent repro. 😕
Otherwise what you could check is if any process below WindowsTerminal.exe or related to WSL is suddenly dying when this issue happens (I'd suggest using Process Hacker (now System Informer) or Process Explorer), or a memory dump of WindowsTerminal.exe and OpenConsole.exe once it gets stuck. However I'm not confident that this would help as much as a consistent repro unfortunately...

@lhecker commented on GitHub (Feb 6, 2023): Hmm... Unfortunately for us to debug this, we'd first need a consistent repro. 😕 Otherwise what you could check is if any process below WindowsTerminal.exe or related to WSL is suddenly dying when this issue happens (I'd suggest using [Process Hacker (now System Informer)](https://systeminformer.sourceforge.io/nightly.php) or [Process Explorer](https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer)), or a memory dump of WindowsTerminal.exe and OpenConsole.exe once it gets stuck. However I'm not confident that this would help as much as a consistent repro unfortunately...
claunia commented 2026-01-31 06:40:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 8, 2023):

Hey there! So, this is actually a weird interaction between WSL and the rest of Windows. One of the keys that you're hitting might be Tab or some other thing that triggers completion.

The problem is, tab completion inside WSL is by default very slow1 . It enumerates every .exe and .dll in the Windows system folder.

Unfortunately, this is out of our control. You can turn off the path sharing behavior in the interop settings section of your WSL config.

  1. This is because it automatically copies the Windows %PATH% into PATH on the Linux side. ↩︎

@DHowett commented on GitHub (Feb 8, 2023): Hey there! So, this is actually a weird interaction between WSL and the rest of _Windows_. One of the keys that you're hitting might be <kbd>Tab</kbd> or some other thing that triggers completion. The problem is, tab completion inside WSL is by default very slow[^1]. It enumerates every `.exe` and `.dll` in the Windows system folder. Unfortunately, this is out of our control. You can turn off the path sharing behavior in the [interop settings](https://learn.microsoft.com/en-us/windows/wsl/wsl-config#interop-settings) section of your WSL config. [^1]: This is because it automatically copies the Windows `%PATH%` into `PATH` on the Linux side.
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-Question Needs-Triage Resolution-Answered
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#19318
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?