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

Terminal crashes after extended use with multiple tabs with SSH sessions #4397

New Issue
Closed
opened 2026-01-30 23:45:58 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:45:58 +00:00
Owner
Copy Link

Originally created by @siennathesane on GitHub (Oct 11, 2019).

Environment

Windows build number: 10.0.18999.0
Windows Terminal version (if applicable): 0.5.2762.0

Any other software? No

Steps to reproduce

Work via multiple SSH sessions.

Expected behavior

Terminal continues to function normally.

Actual behavior

Terminal randomly crashes, I haven't found the specific cause. I do have the event data, though.

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2019-10-11T04:37:45.793053500Z" /> 
  <EventRecordID>753</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>boulder</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>WindowsTerminal.exe</Data> 
  <Data>1.0.1910.3002</Data> 
  <Data>5d969447</Data> 
  <Data>TerminalControl.dll</Data> 
  <Data>1.0.1910.3002</Data> 
  <Data>5d96931e</Data> 
  <Data>c0000005</Data> 
  <Data>000000000001a68b</Data> 
  <Data>6a50</Data> 
  <Data>01d57fa8e0a8a2e6</Data> 
  <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2762.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> 
  <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2762.0_x64__8wekyb3d8bbwe\TerminalControl.dll</Data> 
  <Data>b28e87f8-8675-4143-9172-92de557b1410</Data> 
  <Data>Microsoft.WindowsTerminal_0.5.2762.0_x64__8wekyb3d8bbwe</Data> 
  <Data>App</Data> 
  </EventData>
  </Event>
Originally created by @siennathesane on GitHub (Oct 11, 2019). # Environment ```none Windows build number: 10.0.18999.0 Windows Terminal version (if applicable): 0.5.2762.0 Any other software? No ``` # Steps to reproduce Work via multiple SSH sessions. # Expected behavior Terminal continues to function normally. # Actual behavior Terminal randomly crashes, I haven't found the specific cause. I do have the event data, though. ```xml <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-10-11T04:37:45.793053500Z" /> <EventRecordID>753</EventRecordID> <Channel>Application</Channel> <Computer>boulder</Computer> <Security /> </System> - <EventData> <Data>WindowsTerminal.exe</Data> <Data>1.0.1910.3002</Data> <Data>5d969447</Data> <Data>TerminalControl.dll</Data> <Data>1.0.1910.3002</Data> <Data>5d96931e</Data> <Data>c0000005</Data> <Data>000000000001a68b</Data> <Data>6a50</Data> <Data>01d57fa8e0a8a2e6</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2762.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2762.0_x64__8wekyb3d8bbwe\TerminalControl.dll</Data> <Data>b28e87f8-8675-4143-9172-92de557b1410</Data> <Data>Microsoft.WindowsTerminal_0.5.2762.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> ```
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-Repro labels 2026-01-30 23:45:58 +00:00
claunia commented 2026-01-30 23:45:59 +00:00
Author
Owner
Copy Link

@rennex commented on GitHub (Oct 11, 2019):

Here too, I've been using Terminal for about a week (1-2 windows open, usually with a few WSL tabs in each), and I see at least one crash a day. My version is also 0.5.2762.0.

I doubt SSH has anything to do with it though. Whatever software runs in WSL doesn't concern the Terminal, it just handles console input and output.

@rennex commented on GitHub (Oct 11, 2019): Here too, I've been using Terminal for about a week (1-2 windows open, usually with a few WSL tabs in each), and I see at least one crash a day. My version is also 0.5.2762.0. I doubt SSH has anything to do with it though. Whatever software runs in WSL doesn't concern the Terminal, it just handles console input and output.
claunia commented 2026-01-30 23:45:59 +00:00
Author
Owner
Copy Link

@marksreid-displayr commented on GitHub (Oct 15, 2019):

I have experienced this too. A few tabs, ssh inside wsl, cmd, sqlplus (oracle tool). It will just abort when I'm not even actively using it. Also on version 0.5.2762.0.
Is there an option to enable better collection of crash data?

@marksreid-displayr commented on GitHub (Oct 15, 2019): I have experienced this too. A few tabs, ssh inside wsl, cmd, sqlplus (oracle tool). It will just abort when I'm not even actively using it. Also on version 0.5.2762.0. Is there an option to enable better collection of crash data?
claunia commented 2026-01-30 23:45:59 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 23, 2019):

This might be a bit better as of v0.6. Would you mind reporting whether you still see sporadic crashes once you've updated?
Thanks!

@DHowett-MSFT commented on GitHub (Oct 23, 2019): This might be a bit better as of v0.6. Would you mind reporting whether you still see sporadic crashes once you've updated? Thanks!
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 Needs-Triage Resolution-No-Repro
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#4397
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?