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

ssh disconnect automaticlly after a period of time. #14851

New Issue
Closed
opened 2026-01-31 04:21:17 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 04:21:17 +00:00
Owner
Copy Link

Originally created by @coby-wang on GitHub (Aug 12, 2021).

Windows Terminal version (or Windows build number)

Microsoft Windows NT 10.0.19043.0

Other Software

OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2

Steps to reproduce

  1. open ssh connection, and then execute a few ssh commands.
  2. do other things and keep the ssh connection.
  3. get back the ssh connection and execute ssh command

Expected Behavior

No response

Actual Behavior

windows terminal response slowly, disconnect ssh automaticlly.
image

Originally created by @coby-wang on GitHub (Aug 12, 2021). ### Windows Terminal version (or Windows build number) Microsoft Windows NT 10.0.19043.0 ### Other Software OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2 ### Steps to reproduce 1. open ssh connection, and then execute a few ssh commands. 2. do other things and keep the ssh connection. 3. get back the ssh connection and execute ssh command ### Expected Behavior _No response_ ### Actual Behavior windows terminal response slowly, disconnect ssh automaticlly. ![image](https://user-images.githubusercontent.com/73372253/129134049-3c99e3a2-a2fd-4d09-8320-a4dcf0d29b32.png)
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 04:21:17 +00:00
claunia commented 2026-01-31 04:21:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 12, 2021):

Does this repro in a vintage console window (i.e. conhost.exe, like by launching cmd.exe directly)? If so, then I'm expecting that this isn't a Terminal-specific issue and is something that should be reported over at https://github.com/powershell/win32-openssh/

@zadjii-msft commented on GitHub (Aug 12, 2021): Does this repro in a vintage console window (i.e. `conhost.exe`, like by launching `cmd.exe` directly)? If so, then I'm expecting that this isn't a Terminal-specific issue and is something that should be reported over at https://github.com/powershell/win32-openssh/
claunia commented 2026-01-31 04:21:18 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Aug 12, 2021):

This got alittle better a few releases ago or something like that but I suspect it's a bit of both win32 openssh and wt. cmd doesn't do it for as long as wt though certainly still a delay. I'll do another comparison to see how long each takes. I constantly use ssh and it's easy to repro this if you have a low ssh timeout period set in the ssh config on the remote host. I will note, it has always seemed to be a bit faster in response with ssh used in WSL but still not immediate like Mintty or Putty are.

@WSLUser commented on GitHub (Aug 12, 2021): This got alittle better a few releases ago or something like that but I suspect it's a bit of both win32 openssh and wt. cmd doesn't do it for as long as wt though certainly still a delay. I'll do another comparison to see how long each takes. I constantly use ssh and it's easy to repro this if you have a low ssh timeout period set in the ssh config on the remote host. I will note, it has always seemed to be a bit faster in response with ssh used in WSL but still not immediate like Mintty or Putty are.
claunia commented 2026-01-31 04:21:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 12, 2021):

This got alittle better a few releases ago or something like that but I suspect ... wt.

WT knows nothing about the SSH protocol and makes no endeavour to implement a process timeout of any kind. Speculation that WT is involved is specious.

@DHowett commented on GitHub (Aug 12, 2021): > This got alittle better a few releases ago or something like that but I suspect ... wt. WT knows nothing about the SSH protocol and makes no endeavour to implement a process timeout of any kind. Speculation that WT is involved is specious.
claunia commented 2026-01-31 04:21:18 +00:00
Author
Owner
Copy Link

@coby-wang commented on GitHub (Aug 13, 2021):

OK, thanks for your attention. I'll keep watching.

@coby-wang commented on GitHub (Aug 13, 2021): OK, thanks for your attention. I'll keep watching.
claunia commented 2026-01-31 04:21:18 +00:00
Author
Owner
Copy Link

@Arbureva commented on GitHub (Feb 9, 2023):

OK, thanks for your attention. I'll keep watching.

Have you solved this problem now?

@Arbureva commented on GitHub (Feb 9, 2023): > OK, thanks for your attention. I'll keep watching. Have you solved this problem now?
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-Attention Needs-Tag-Fix 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#14851
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?