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 hangs when hitting Ctrl-C many times #5250

New Issue
Closed
opened 2026-01-31 00:08:37 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:08:37 +00:00
Owner
Copy Link

Originally created by @doggy8088 on GitHub (Nov 27, 2019).

Environment

Windows build number: 10.0.18363.476
Windows Terminal version (if applicable): 0.7.3291.0

Steps to reproduce

  1. Open Windows Terminal
  2. Run cmd shell
  3. Hit Ctrl-C twice very quickly.
  4. Then the cmd shell just hangs.

Expected behavior

It should show up prompt after hitting Ctrl-C many times.

Actual behavior

The shell window get hang.

Here is a video clip that shows the situation. The demo contains two keystroke, the first is simply Ctrl-C, the second one if hit Ctrl-C twice very quickly.

2019-11-28_00-28-06

Originally created by @doggy8088 on GitHub (Nov 27, 2019). # Environment ```none Windows build number: 10.0.18363.476 Windows Terminal version (if applicable): 0.7.3291.0 ``` # Steps to reproduce 1. Open Windows Terminal 2. Run **cmd** shell 3. Hit `Ctrl-C` twice very quickly. 4. Then the **cmd** shell just hangs. # Expected behavior It should show up prompt after hitting `Ctrl-C` many times. # Actual behavior The shell window get hang. Here is a video clip that shows the situation. The demo contains two keystroke, the first is simply `Ctrl-C`, the second one if hit `Ctrl-C` twice very quickly. ![2019-11-28_00-28-06](https://user-images.githubusercontent.com/88981/69741488-17b87880-1176-11ea-8182-fb768c60e06d.gif)
claunia added the Needs-Tag-Fix label 2026-01-31 00:08:37 +00:00
claunia commented 2026-01-31 00:08:38 +00:00
Author
Owner
Copy Link

@GaganBhat commented on GitHub (Dec 1, 2019):

I am not able to reproduce this on 10.0.19025.1051 (possibly fixed so this issue should be closed?). For some reason, it looks like your terminal is doing something that the exit command causes.

3OoQdPFctq

@GaganBhat commented on GitHub (Dec 1, 2019): I am not able to reproduce this on `10.0.19025.1051` (possibly fixed so this issue should be closed?). For some reason, it looks like your terminal is doing something that the `exit` command causes. ![3OoQdPFctq](https://user-images.githubusercontent.com/25236969/69918211-14064980-1435-11ea-90e1-6439969c7a58.gif)
claunia commented 2026-01-31 00:08:38 +00:00
Author
Owner
Copy Link

@doggy8088 commented on GitHub (Dec 1, 2019):

The problem is gone for now. I don't know why.

@doggy8088 commented on GitHub (Dec 1, 2019): The problem is gone for now. I don't know why.
claunia commented 2026-01-31 00:08:38 +00:00
Author
Owner
Copy Link

@sterlingdcs-damian commented on GitHub (Aug 23, 2023):

This is still an issue

@sterlingdcs-damian commented on GitHub (Aug 23, 2023): This is still an issue
claunia commented 2026-01-31 00:08:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 24, 2023):

@sterlingdcs-damian

This issue was closed 4 years ago. Please consider opening a new issue instead of leaving a comment here.

If you're still seeing something like this, then I'm sure it has a different root cause than whatever was causing this 22 releases of the Terminal ago

@zadjii-msft commented on GitHub (Aug 24, 2023): @sterlingdcs-damian > This issue was closed 4 years ago. Please consider opening a [new issue](https://github.com/microsoft/terminal/issues/new/choose) instead of leaving a comment here. If you're still seeing something like this, then I'm sure it has a different root cause than whatever was causing this _22 releases of the Terminal ago_
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 Needs-Tag-Fix
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#5250
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?