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

Indefinite Random lag when using Git Bash #23112

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

Originally created by @RushilJalal on GitHub (Apr 4, 2025).

Windows Terminal version

1.22.10731.0

Windows build number

26100.3624

Other Software

Git Bash git version 2.45.2.windows.1

Steps to reproduce

This is completely random.

Expected Behavior

I expect no lags of this nature.

Actual Behavior

the cursor keeps blinking but no reflection of keyboard keystrokes.
Sometimes, after a while(10-15 seconds), all the text which was typed while the terminal was stuck, appears at the same time.

Originally created by @RushilJalal on GitHub (Apr 4, 2025). ### Windows Terminal version 1.22.10731.0 ### Windows build number 26100.3624 ### Other Software Git Bash git version 2.45.2.windows.1 ### Steps to reproduce This is completely random. ### Expected Behavior I expect no lags of this nature. ### Actual Behavior the cursor keeps blinking but no reflection of keyboard keystrokes. Sometimes, after a while(10-15 seconds), all the text which was typed while the terminal was stuck, appears at the same time.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:32:43 +00:00
claunia commented 2026-01-31 08:32:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 9, 2025):

Hey, that's weird!

Does this happen when you run Git Bash outside of Windows Terminal?

If you press control keys when it's stuck like this, e.g. Ctrl+C or Ctrl+Q, does anything happen/?

@DHowett commented on GitHub (Apr 9, 2025): Hey, that's weird! Does this happen when you run Git Bash _outside_ of Windows Terminal? If you press control keys when it's stuck like this, e.g. <kbd>Ctrl+C</kbd> or <kbd>Ctrl+Q</kbd>, does anything happen/?
claunia commented 2026-01-31 08:32:45 +00:00
Author
Owner
Copy Link

@RushilJalal commented on GitHub (Apr 10, 2025):

@DHowett No, this does not happen when running Git Bash in its own window.

Nothing happens when I press the above shortcut keys. The cursor keeps blinking and the window is completely unresponsive.

@RushilJalal commented on GitHub (Apr 10, 2025): @DHowett No, this does not happen when running Git Bash in its own window. Nothing happens when I press the above shortcut keys. The cursor keeps blinking and the window is completely unresponsive.
claunia commented 2026-01-31 08:32:45 +00:00
Author
Owner
Copy Link

@RushilJalal commented on GitHub (Apr 10, 2025):

I noticed this issue is reproducible when i am focused on the Windows Terminal running Git Bash and I click Tab twice.
I ensure that the window hasn't lost focus but yet it stops taking input.
Otherwise, its a random issue.

Also, it started working after 20 seconds or so.

@RushilJalal commented on GitHub (Apr 10, 2025): I noticed this issue is reproducible when i am focused on the Windows Terminal running Git Bash and I click Tab twice. I ensure that the window hasn't lost focus but yet it stops taking input. Otherwise, its a random issue. Also, it started working after 20 seconds or so.
claunia commented 2026-01-31 08:32:46 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 10, 2025):

Wait a sec - you have to press tab?

This will break your existing session (so don't do it on anything you care about,) but if you set...

export PATH=/bin

and then press Tab a couple times, does it still hang?

@DHowett commented on GitHub (Apr 10, 2025): Wait a sec - you have to press tab? This will break your existing session (so don't do it on anything you care about,) but if you set... ``` export PATH=/bin ``` and then press <kbd>Tab</kbd> a couple times, does it still hang?
claunia commented 2026-01-31 08:32:46 +00:00
Author
Owner
Copy Link

@RushilJalal commented on GitHub (Apr 11, 2025):

Yeppp, setting the above command in the .bash-profile fixed it for now.

Although, don't you think this should be set by default?

P.S I noticed commands like npm install -g @angular/cli or any other npm command stop working and throws the error npm: Not Found after setting the above PATH.

My current .bash_profile:

export BUN_INSTALL="$HOME/.bun"
export PATH=$BUN_INSTALL/bin:$PATH
#export PATH=/bin  <- commented since other commands stop working when I use this
@RushilJalal commented on GitHub (Apr 11, 2025): Yeppp, setting the above command in the `.bash-profile` fixed it for now. Although, don't you think this should be set by default? P.S I noticed commands like `npm install -g @angular/cli` or any other `npm` command stop working and throws the error `npm: Not Found` after setting the above PATH. My current `.bash_profile`: ```bash export BUN_INSTALL="$HOME/.bun" export PATH=$BUN_INSTALL/bin:$PATH #export PATH=/bin <- commented since other commands stop working when I use this ```
claunia commented 2026-01-31 08:32:47 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 14, 2025):

Well, so, here's what's happening.

Tab invokes tab completion. Tab completion at the beginning of a prompt searches for a command in the PATH.

Your PATH contains a lot of folders.

Every time you press Tab, it has to search all of those folders. This is a slow operation.

This isn't Terminal's doing, mind you. This is how your shell handles tab completion. It would be true in any shell that offers tab completion.

Setting PATH to /bin tells the shell "don't look for commands anywhere except /bin". This applies to both tab completion and normal command execution. That's why it breaks npm, of course.

But that's also why it makes a good diagnostic.

Since it works after setting the PATH to be very short, it proves that your problem is tab completion. It's not intended to be a fix, just a test.

Unfortunately, your actual issue lies somewhere outside of Terminal.

@DHowett commented on GitHub (Apr 14, 2025): Well, so, here's what's happening. <kbd>Tab</kbd> invokes tab completion. Tab completion at the beginning of a prompt searches for a command in the `PATH`. Your `PATH` contains a lot of folders. Every time you press <kbd>Tab</kbd>, it has to search _all of those folders_. This is a slow operation. This isn't Terminal's doing, mind you. This is how your shell handles tab completion. It would be true in any shell that offers tab completion. Setting `PATH` to `/bin` tells the shell "don't look for commands anywhere except `/bin`". This applies to both tab completion _and_ normal command execution. That's why it breaks `npm`, of course. But that's also why it makes a good diagnostic. Since it works after setting the `PATH` to be very short, it proves that your problem is tab completion. It's not intended to be a _fix,_ just a test. Unfortunately, your actual issue lies somewhere outside of Terminal.
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#23112
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?