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

Terminal App Version 1.8.1521.0 crashes on openssh client connection exit (WSL2 Ubuntu buster/sid Linux) #14508

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

Originally created by @ministry-of-code on GitHub (Jul 14, 2021).

Windows Terminal version (or Windows build number)

Terminal App Version 1.8.1521.0

Other Software

openssh on Linux WSL2 (Ubuntu)

Steps to reproduce

Sometimes, not always, the Terminal App crashes when I log off of a SSH connection to a remote (Linux) Server. I run WSL2 with Ubuntu Linux 4.19.84-microsoft-standard+ #1 SMP Fri Mar 19 11:33:09 CET 2021 x86_64 x86_64 x86_64 GNU/Linux.

This is really really a showstopper for my productive work. I have many tabs and server connections open and when the terminal app crashes, all those connections and open files, etc are lost!

Expected Behavior

Terminal app does not crash

Actual Behavior

Terminal app crashes

Originally created by @ministry-of-code on GitHub (Jul 14, 2021). ### Windows Terminal version (or Windows build number) Terminal App Version 1.8.1521.0 ### Other Software openssh on Linux WSL2 (Ubuntu) ### Steps to reproduce Sometimes, not always, the Terminal App crashes when I log off of a SSH connection to a remote (Linux) Server. I run WSL2 with Ubuntu Linux 4.19.84-microsoft-standard+ #1 SMP Fri Mar 19 11:33:09 CET 2021 x86_64 x86_64 x86_64 GNU/Linux. This is really really a showstopper for my productive work. I have many tabs and server connections open and when the terminal app crashes, all those connections and open files, etc are lost! ### Expected Behavior Terminal app does not crash ### Actual Behavior Terminal app crashes
claunia commented 2026-01-31 04:12:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 14, 2021):

Could you repro this with the Feedback hub? That'll get us a stack trace we can use to root-cause this

/feedback

@zadjii-msft commented on GitHub (Jul 14, 2021): Could you repro this with the Feedback hub? That'll get us a stack trace we can use to root-cause this /feedback
claunia commented 2026-01-31 04:12:12 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2021):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Jul 14, 2021): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 04:12:12 +00:00
Author
Owner
Copy Link

@ministry-of-code commented on GitHub (Jul 14, 2021):

Could you repro this with the Feedback hub? That'll get us a stack trace we can use to root-cause this

/feedback

@zadjii-msft thanks for the feedback. I have submitted an issue via the Feedback hub two weeks ago:

https://aka.ms/AAd71do

Does this help?

@ministry-of-code commented on GitHub (Jul 14, 2021): > Could you repro this with the Feedback hub? That'll get us a stack trace we can use to root-cause this > > /feedback @zadjii-msft thanks for the feedback. I have submitted an issue via the Feedback hub two weeks ago: https://aka.ms/AAd71do Does this help?
claunia commented 2026-01-31 04:12:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 14, 2021):

Oh no, just open the feedback hub and draft up the feedback, then the last step will ask you for a recording of the issue. Start the recording, then switch over to the Terminal and repro the bug, then switch back and end the recording. The Feedback Hub will automatically collect up the crash that happened during the recording and link it with the feedback. Submit the feedback, and share the aka.ms URL here, and we can then go look up the crash on the backend. Neat!

@zadjii-msft commented on GitHub (Jul 14, 2021): Oh no, just open the feedback hub and draft up the feedback, then the last step will ask you for a recording of the issue. Start the recording, then switch over to the Terminal and repro the bug, then switch back and end the recording. The Feedback Hub will automatically collect up the crash that happened during the recording and link it with the feedback. Submit the feedback, and share the aka.ms URL here, and we can then go look up the crash on the backend. Neat!
claunia commented 2026-01-31 04:12:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 14, 2021):

(unfortunately, the original feedback you filed didn't collect up the crash, so it doesn't have anything helpful in it 😢)

@zadjii-msft commented on GitHub (Jul 14, 2021): (unfortunately, the original feedback you filed didn't collect up the crash, so it doesn't have anything helpful in it 😢)
claunia commented 2026-01-31 04:12:13 +00:00
Author
Owner
Copy Link

@ministry-of-code commented on GitHub (Jul 14, 2021):

Ok, I understand. Unfortunately, I can not start the diagnose process in the Feedback hub app. When I try to start it for the windows-terminal app, I get an error message telling me that it did not work and I should try it again:

image

@ministry-of-code commented on GitHub (Jul 14, 2021): Ok, I understand. Unfortunately, I can not start the diagnose process in the Feedback hub app. When I try to start it for the windows-terminal app, I get an error message telling me that it did not work and I should try it again: ![image](https://user-images.githubusercontent.com/2571417/125629526-052f9e0c-8dc7-4b8a-9839-47565e1ca1d6.png)
claunia commented 2026-01-31 04:12:13 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jul 14, 2021):

To ensure WSL2 isn't involved, are you using the default kernel or a custom one? If it's custom, what's different from the default WSL2 kernel? Technically this shouldn't matter unless something with the console options was changed or possibly even network config since ssh is involved.

@WSLUser commented on GitHub (Jul 14, 2021): To ensure WSL2 isn't involved, are you using the default kernel or a custom one? If it's custom, what's different from the default WSL2 kernel? Technically this shouldn't matter unless something with the console options was changed or possibly even network config since ssh is involved.
claunia commented 2026-01-31 04:12:13 +00:00
Author
Owner
Copy Link

@ministry-of-code commented on GitHub (Jul 15, 2021):

To ensure WSL2 isn't involved, are you using the default kernel or a custom one? If it's custom, what's different from the default WSL2 kernel? Technically this shouldn't matter unless something with the console options was changed or possibly even network config since ssh is involved.

You're right, I am using a custom WSL2 Kernel Configuration (based on the official MS WSL2-Kernel). I can't remember why I did this (it's a couple of months ago that I compiled it) - but it must have had an important reason - probably to fix a network related problem (docker, localhost forwarding or such). I will disable the custom kernel and use the official one again and see if this solves the crash or not and will come back in a few days to report.

@ministry-of-code commented on GitHub (Jul 15, 2021): > To ensure WSL2 isn't involved, are you using the default kernel or a custom one? If it's custom, what's different from the default WSL2 kernel? Technically this shouldn't matter unless something with the console options was changed or possibly even network config since ssh is involved. You're right, I am using a custom WSL2 Kernel Configuration (based on the official MS WSL2-Kernel). I can't remember why I did this (it's a couple of months ago that I compiled it) - but it must have had an important reason - probably to fix a network related problem (docker, localhost forwarding or such). I will disable the custom kernel and use the official one again and see if this solves the crash or not and will come back in a few days to report.
claunia commented 2026-01-31 04:12:13 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jul 15, 2021):

FWIW I tested this on my custom kernel and has no issues. I'm also running 1.10 Preview now but I never had issues before that I could recall. My custom kernel is compiled from the 5.12 stable with the MS specific patches merged and my config options, which do enable some networking stuff, particularly for docker/kind/k3d, etc.

I'd still recommend testing with default 5.10.x kernel from WSL2 repo to reduce the factors.

@WSLUser commented on GitHub (Jul 15, 2021): FWIW I tested this on my custom kernel and has no issues. I'm also running 1.10 Preview now but I never had issues before that I could recall. My custom kernel is compiled from the 5.12 stable with the MS specific patches merged and my config options, which do enable some networking stuff, particularly for docker/kind/k3d, etc. I'd still recommend testing with default 5.10.x kernel from WSL2 repo to reduce the factors.
claunia commented 2026-01-31 04:12:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 19, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 19, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#14508
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?