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

Windows Terminal crashing, TermControlAutomationPeer::RecordKeyEvent and InteractivityAutomationPeer::NotifyNewOutput #19115

New Issue
Closed
opened 2026-01-31 06:34:14 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:34:14 +00:00
Owner
Copy Link

Originally created by @bambery on GitHub (Dec 22, 2022).

Originally assigned to: @carlos-zamora on GitHub.

Windows Terminal version

1.15.2212.12006, also 1.16.2212.12004

Windows build number

10.0.22000.0

Other Software

all within WSL2:
vim 8.1.3741
node 18.9.1
jest 8.19.1

Steps to reproduce

I cannot force this problem to occur, but it has happened twice today, and several times in the last few weeks when I am using Terminal on WSL2 and working in Vim.

I included details that I was running some React tests, but I had this problem several times last week when I was working in Python (no framework).

I went back through the event logs and the earliest date of this error is 8/17/22. There are 8 total logs since then which are nearly identical to the ones below. I've spent a large amount of time on this computer since then, much of it with a vim window open somewhere, so this is a relatively rare issue. However, twice in one day is a bit much.

Expected Behavior

No response

Actual Behavior

When I am working in Vim, when I am changing focus between Terminal and another app (in this case, I was running a react debugger in chrome), occasionally Terminal will crash without any errors. This happens whether I change focus with alt+tab or with the mouse.

I cannot be certain changing focus is what is triggering the issue, since I change focus frequently, but it has not happened when I am just typing happily into Vim, nor when I switch between Vim panes.

I was running the terminal preview when it crashed, so I switched to the non-preview (hence the two version numbers for Terminal) and had the same issue.

Here are the event logs for these crashes:
For the first crash today at 2:52:24 (using Terminal Preview):

ERROR:

Faulting application name: WindowsTerminal.exe, version: 1.16.2212.12004, time stamp: 0x6397c31c
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.16.2212.12004, time stamp: 0x6397c12e
Exception code: 0xc0000005
Fault offset: 0x00000000000d5112
Faulting process id: 0x4680
Faulting application start time: 0x01d914b7036683d3
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: efaf5abb-faf8-4f7c-aba5-aefc5999d1e5
Faulting package full name: Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

WINDOWS ERROR REPORTING:

Fault bucket 1477357042843758786, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.16.2212.12004
P4: 6397c31c
P5: Microsoft.Terminal.Control.dll
P6: 1.16.2212.12004
P7: 6397c12e
P8: c0000005
P9: 00000000000d5112
P10:

Attached files:
[buncha files]

These files may be available here:
[link to a wer file]

Analysis symbol:
Rechecking for solution: 0
Report Id: efaf5abb-faf8-4f7c-aba5-aefc5999d1e5
Report Status: 268435456
Hashed bucket: 9f45178bb05e9a32c480a067311fb0c2
Cab Guid: 0

for the second crash at 6:50:59 (with non preview):

ERROR:

Faulting application name: WindowsTerminal.exe, version: 1.15.2212.12006, time stamp: 0x6397f53c
Faulting module name: Microsoft.Terminal.Control.dll, version: 1.15.2212.12006, time stamp: 0x6397f373
Exception code: 0xc0000005
Fault offset: 0x00000000000b2bd9
Faulting process id: 0x7f0
Faulting application start time: 0x01d915801c4096a8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll
Report Id: 47cfed3e-ccc3-44b4-90eb-fbeb40eabd52
Faulting package full name: Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

WINDOWS ERROR REPORTING:

Fault bucket 2089511070221908304, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.15.2212.12006
P4: 6397f53c
P5: Microsoft.Terminal.Control.dll
P6: 1.15.2212.12006
P7: 6397f373
P8: c000041d
P9: 00000000000b2bd9
P10:

Attached files:
[buncha files]

These files may be available here:
[link to a wer file]

Analysis symbol:
Rechecking for solution: 0
Report Id: 8a9de9e7-2bbd-4d46-8a3e-d7c0b3dee0b7
Report Status: 268435456
Hashed bucket: 01b156f5f7ca4192ccff6f3f66d2b950
Cab Guid: 0

Originally created by @bambery on GitHub (Dec 22, 2022). Originally assigned to: @carlos-zamora on GitHub. ### Windows Terminal version 1.15.2212.12006, also 1.16.2212.12004 ### Windows build number 10.0.22000.0 ### Other Software all within WSL2: vim 8.1.3741 node 18.9.1 jest 8.19.1 ### Steps to reproduce I cannot force this problem to occur, but it has happened twice today, and several times in the last few weeks when I am using Terminal on WSL2 and working in Vim. I included details that I was running some React tests, but I had this problem several times last week when I was working in Python (no framework). I went back through the event logs and the earliest date of this error is 8/17/22. There are 8 total logs since then which are nearly identical to the ones below. I've spent a large amount of time on this computer since then, much of it with a vim window open somewhere, so this is a relatively rare issue. However, twice in one day is a bit much. ### Expected Behavior _No response_ ### Actual Behavior When I am working in Vim, when I am changing focus between Terminal and another app (in this case, I was running a react debugger in chrome), occasionally Terminal will crash without any errors. This happens whether I change focus with alt+tab or with the mouse. I cannot be certain changing focus is what is triggering the issue, since I change focus frequently, but it has not happened when I am just typing happily into Vim, nor when I switch between Vim panes. I was running the terminal preview when it crashed, so I switched to the non-preview (hence the two version numbers for Terminal) and had the same issue. Here are the event logs for these crashes: For the first crash today at 2:52:24 (using Terminal Preview): ERROR: *** Faulting application name: WindowsTerminal.exe, version: 1.16.2212.12004, time stamp: 0x6397c31c Faulting module name: Microsoft.Terminal.Control.dll, version: 1.16.2212.12004, time stamp: 0x6397c12e Exception code: 0xc0000005 Fault offset: 0x00000000000d5112 Faulting process id: 0x4680 Faulting application start time: 0x01d914b7036683d3 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Report Id: efaf5abb-faf8-4f7c-aba5-aefc5999d1e5 Faulting package full name: Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App WINDOWS ERROR REPORTING: *** Fault bucket 1477357042843758786, type 5 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminalPreview_1.16.3464.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.16.2212.12004 P4: 6397c31c P5: Microsoft.Terminal.Control.dll P6: 1.16.2212.12004 P7: 6397c12e P8: c0000005 P9: 00000000000d5112 P10: Attached files: [buncha files] These files may be available here: [link to a wer file] Analysis symbol: Rechecking for solution: 0 Report Id: efaf5abb-faf8-4f7c-aba5-aefc5999d1e5 Report Status: 268435456 Hashed bucket: 9f45178bb05e9a32c480a067311fb0c2 Cab Guid: 0 for the second crash at 6:50:59 (with non preview): ERROR: *** Faulting application name: WindowsTerminal.exe, version: 1.15.2212.12006, time stamp: 0x6397f53c Faulting module name: Microsoft.Terminal.Control.dll, version: 1.15.2212.12006, time stamp: 0x6397f373 Exception code: 0xc0000005 Fault offset: 0x00000000000b2bd9 Faulting process id: 0x7f0 Faulting application start time: 0x01d915801c4096a8 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Control.dll Report Id: 47cfed3e-ccc3-44b4-90eb-fbeb40eabd52 Faulting package full name: Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App WINDOWS ERROR REPORTING: *** Fault bucket 2089511070221908304, type 5 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminal_1.15.3466.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.15.2212.12006 P4: 6397f53c P5: Microsoft.Terminal.Control.dll P6: 1.15.2212.12006 P7: 6397f373 P8: c000041d P9: 00000000000b2bd9 P10: Attached files: [buncha files] These files may be available here: [link to a wer file] Analysis symbol: Rechecking for solution: 0 Report Id: 8a9de9e7-2bbd-4d46-8a3e-d7c0b3dee0b7 Report Status: 268435456 Hashed bucket: 01b156f5f7ca4192ccff6f3f66d2b950 Cab Guid: 0
claunia commented 2026-01-31 06:34:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 3, 2023):

Wow for once, the EV logs here actually did point at a crash on the backend! That's amazing!

For MSFT folks, BucketDetails?BucketIdentifier=9f45178b-b05e-9a32-c480-a067311fb0c2.

There's multiple crashes in here, MSFT:38673750 and MSFT:38745829. These are blamed to ...Control::implementation::TermControlAutomationPeer::NotifyNewOutput and ...Control::implementation::TermControlAutomationPeer::RecordKeyEvent respectively.

These stacks are weird though, not sure what regressed here
image

image

I may need to dig into stacks closer. There's plenty of dumps so we should have something to go on.

@zadjii-msft commented on GitHub (Jan 3, 2023): Wow for once, the EV logs here actually _did_ point at a crash on the backend! That's amazing! For MSFT folks, `BucketDetails?BucketIdentifier=9f45178b-b05e-9a32-c480-a067311fb0c2`. There's multiple crashes in here, MSFT:38673750 and MSFT:38745829. These are blamed to `...Control::implementation::TermControlAutomationPeer::NotifyNewOutput` and `...Control::implementation::TermControlAutomationPeer::RecordKeyEvent` respectively. These stacks are weird though, not sure what regressed here ![image](https://user-images.githubusercontent.com/18356694/210384820-799fce3b-70ea-49e2-85e6-06f5c9307420.png) ![image](https://user-images.githubusercontent.com/18356694/210384686-0a8bf9fb-4d84-4565-9f4c-f678adecf29c.png) I may need to dig into stacks closer. There's plenty of dumps so we should have something to go on.
claunia commented 2026-01-31 06:34:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 24, 2023):

:tada:This issue was addressed in #14694, which has now been successfully released as Windows Terminal v1.16.1023 (10231 and 10232).🎉

Handy links:

@ghost commented on GitHub (Jan 24, 2023): :tada:This issue was addressed in #14694, which has now been successfully released as `Windows Terminal v1.16.1023 (10231 and 10232)`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.16.1023 (10231 and 10232)) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 06:34:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 24, 2023):

:tada:This issue was addressed in #14694, which has now been successfully released as Windows Terminal Preview v1.17.1023.🎉

Handy links:

@ghost commented on GitHub (Jan 24, 2023): :tada:This issue was addressed in #14694, which has now been successfully released as `Windows Terminal Preview v1.17.1023`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.17.1023) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 Area-TerminalControl Issue-Bug Product-Terminal Resolution-Fix-Committed Severity-Crash
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#19115
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?