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

FAST_FAIL_FATAL_APP_EXIT during defapp invocation after logon #15931

New Issue
Open
opened 2026-01-31 04:52:31 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:52:31 +00:00
Owner
Copy Link

Originally created by @ianjoneill on GitHub (Nov 20, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.22000.318

Other Software

No response

Steps to reproduce

Unfortunately this just happened with no interaction following logon, however I don't have windows terminal set to start up on logon.

This makes me think it must have been a defapp invocation because I certainly didn't trigger it. The app appeared for a split second, then disappeared.

Expected Behavior

No response

Actual Behavior

Crash dump appeared in %LOCALAPPDATA%\CrashDumps.

Can provide the dump by email if that would be useful.

WinDbg output:

0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7249

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 169477

    Key  : Analysis.Init.CPU.mSec
    Value: 608

    Key  : Analysis.Init.Elapsed.mSec
    Value: 43767

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 322

    Key  : FailFast.Name
    Value: FATAL_APP_EXIT

    Key  : FailFast.Type
    Value: 7

    Key  : Timeline.Process.Start.DeltaSec
    Value: 1

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1

    Key  : WER.Process.Version
    Value: 1.11.2110.19001


FILE_IN_CAB:  WindowsTerminal.exe.22988.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=0000000000000001 rbx=00000015524ff460 rcx=0000000000000007
rdx=000000000000000f rsi=00000015524fea40 rdi=00000000ffffffff
rip=00007ff83b98dd7e rsp=00000015524fe0f0 rbp=00000015524fe250
 r8=0000000000000001  r9=00000015524fe098 r10=0000000000000012
r11=0000200200000000 r12=0000000000000000 r13=00000015524fec20
r14=00000015524fe400 r15=00000015524fe430
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
ucrtbase!abort+0x4e:
00007ff8`3b98dd7e cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff83b98dd7e (ucrtbase!abort+0x000000000000004e)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000007
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT 

PROCESS_NAME:  WindowsTerminal.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000007

STACK_TEXT:  
00000015`524fe0f0 00007ff8`3b98d499     : 00000015`00000003 00000015`00000003 00007fff`f71f62b0 00007fff`f71f6280 : ucrtbase!abort+0x4e
00000015`524fe120 00007ff8`0a101aab     : 00000015`524ff460 00000015`524fea40 00000015`524fe400 00000015`524fe400 : ucrtbase!terminate+0x29
00000015`524fe150 00007ff8`0a102317     : 00007fff`effd33a3 00007fff`efffc18c 00000015`524fe370 00007fff`f71e2519 : VCRUNTIME140_1!FindHandler<__FrameHandler4>+0x45b
00000015`524fe320 00007ff8`0a1040d9     : 00007ff7`f4090000 00000015`524ff460 00000015`524fec20 00000015`524fea40 : VCRUNTIME140_1!__InternalCxxFrameHandler<__FrameHandler4>+0x267
00000015`524fe3c0 00007ff7`f409ef84     : 00000015`524ff7b0 00007ff7`f40c3dcc 00000015`524ff460 00000015`524ff7b0 : VCRUNTIME140_1!__CxxFrameHandler4+0xa9
00000015`524fe430 00007ff8`3dc482ff     : 00000000`00000000 00000015`524fe9f0 00000015`524ff460 00000000`00000081 : WindowsTerminal+0xef84
00000015`524fe460 00007ff8`3dbd5a0a     : 00000015`524ff460 00007ff7`f4090000 00007ff7`f40969c5 00007ff7`f40cd39c : ntdll!RtlpExecuteHandlerForException+0xf
00000015`524fe490 00007ff8`3dbd2cd3     : 00000000`00000000 00000015`524ff310 00000000`00000000 00007ff8`3dbd2c3f : ntdll!RtlDispatchException+0x25a
00000015`524febe0 00007ff8`3b56466c     : 00000000`00000000 00007ff7`f40c8170 00000015`524ff5b0 00000000`00000000 : ntdll!RtlRaiseException+0x163
00000015`524ff440 00007fff`f71e6480     : 00000000`00000000 00000000`00000000 00000000`00000000 00007ff8`3dbc8db8 : KERNELBASE!RaiseException+0x6c
00000015`524ff520 00007ff7`f40a0bfb     : 00000118`baf05d30 00000000`800706be 00000000`800706be 00000118`bafa6160 : VCRUNTIME140!_CxxThrowException+0x90
00000015`524ff580 00007ff7`f40a26d6     : 00000118`bafa99d0 00000118`bafa99d0 00000118`bafa6160 00000118`bafa6148 : WindowsTerminal+0x10bfb
00000015`524ff5e0 00007ff7`f40969c5     : 00000000`00000000 00000118`bae5a258 00000015`524ffb88 00000015`524ffb70 : WindowsTerminal+0x126d6
00000015`524ff7b0 00007ff7`f409878e     : 00000000`0000000a 00000000`0000000a 00000000`00000000 00000000`00000000 : WindowsTerminal+0x69c5
00000015`524ffa80 00007ff7`f409bf72     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0x878e
00000015`524ffc40 00007ff8`3c8854e0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0xbf72
00000015`524ffc80 00007ff8`3dba485b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x10
00000015`524ffcb0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b


SYMBOL_NAME:  ucrtbase!abort+4e

MODULE_NAME: ucrtbase

IMAGE_NAME:  ucrtbase.dll

STACK_COMMAND:  ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID:  FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  10.0.22000.1

FAILURE_ID_HASH:  {e31753ac-c98a-8055-3663-47e707543d20}

Followup:     MachineOwner
---------
Originally created by @ianjoneill on GitHub (Nov 20, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.22000.318 ### Other Software _No response_ ### Steps to reproduce Unfortunately this just happened with no interaction following logon, however I don't have windows terminal set to start up on logon. This makes me think it must have been a defapp invocation because I certainly didn't trigger it. The app appeared for a split second, then disappeared. ### Expected Behavior _No response_ ### Actual Behavior Crash dump appeared in `%LOCALAPPDATA%\CrashDumps`. Can provide the dump by email if that would be useful. WinDbg output: ``` 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 7249 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 169477 Key : Analysis.Init.CPU.mSec Value: 608 Key : Analysis.Init.Elapsed.mSec Value: 43767 Key : Analysis.Memory.CommitPeak.Mb Value: 322 Key : FailFast.Name Value: FATAL_APP_EXIT Key : FailFast.Type Value: 7 Key : Timeline.Process.Start.DeltaSec Value: 1 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 Key : WER.Process.Version Value: 1.11.2110.19001 FILE_IN_CAB: WindowsTerminal.exe.22988.dmp NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 APPLICATION_VERIFIER_FLAGS: 0 CONTEXT: (.ecxr) rax=0000000000000001 rbx=00000015524ff460 rcx=0000000000000007 rdx=000000000000000f rsi=00000015524fea40 rdi=00000000ffffffff rip=00007ff83b98dd7e rsp=00000015524fe0f0 rbp=00000015524fe250 r8=0000000000000001 r9=00000015524fe098 r10=0000000000000012 r11=0000200200000000 r12=0000000000000000 r13=00000015524fec20 r14=00000015524fe400 r15=00000015524fe430 iopl=0 nv up ei pl nz na pe nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202 ucrtbase!abort+0x4e: 00007ff8`3b98dd7e cd29 int 29h Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff83b98dd7e (ucrtbase!abort+0x000000000000004e) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000007 Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT PROCESS_NAME: WindowsTerminal.exe ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000007 STACK_TEXT: 00000015`524fe0f0 00007ff8`3b98d499 : 00000015`00000003 00000015`00000003 00007fff`f71f62b0 00007fff`f71f6280 : ucrtbase!abort+0x4e 00000015`524fe120 00007ff8`0a101aab : 00000015`524ff460 00000015`524fea40 00000015`524fe400 00000015`524fe400 : ucrtbase!terminate+0x29 00000015`524fe150 00007ff8`0a102317 : 00007fff`effd33a3 00007fff`efffc18c 00000015`524fe370 00007fff`f71e2519 : VCRUNTIME140_1!FindHandler<__FrameHandler4>+0x45b 00000015`524fe320 00007ff8`0a1040d9 : 00007ff7`f4090000 00000015`524ff460 00000015`524fec20 00000015`524fea40 : VCRUNTIME140_1!__InternalCxxFrameHandler<__FrameHandler4>+0x267 00000015`524fe3c0 00007ff7`f409ef84 : 00000015`524ff7b0 00007ff7`f40c3dcc 00000015`524ff460 00000015`524ff7b0 : VCRUNTIME140_1!__CxxFrameHandler4+0xa9 00000015`524fe430 00007ff8`3dc482ff : 00000000`00000000 00000015`524fe9f0 00000015`524ff460 00000000`00000081 : WindowsTerminal+0xef84 00000015`524fe460 00007ff8`3dbd5a0a : 00000015`524ff460 00007ff7`f4090000 00007ff7`f40969c5 00007ff7`f40cd39c : ntdll!RtlpExecuteHandlerForException+0xf 00000015`524fe490 00007ff8`3dbd2cd3 : 00000000`00000000 00000015`524ff310 00000000`00000000 00007ff8`3dbd2c3f : ntdll!RtlDispatchException+0x25a 00000015`524febe0 00007ff8`3b56466c : 00000000`00000000 00007ff7`f40c8170 00000015`524ff5b0 00000000`00000000 : ntdll!RtlRaiseException+0x163 00000015`524ff440 00007fff`f71e6480 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ff8`3dbc8db8 : KERNELBASE!RaiseException+0x6c 00000015`524ff520 00007ff7`f40a0bfb : 00000118`baf05d30 00000000`800706be 00000000`800706be 00000118`bafa6160 : VCRUNTIME140!_CxxThrowException+0x90 00000015`524ff580 00007ff7`f40a26d6 : 00000118`bafa99d0 00000118`bafa99d0 00000118`bafa6160 00000118`bafa6148 : WindowsTerminal+0x10bfb 00000015`524ff5e0 00007ff7`f40969c5 : 00000000`00000000 00000118`bae5a258 00000015`524ffb88 00000015`524ffb70 : WindowsTerminal+0x126d6 00000015`524ff7b0 00007ff7`f409878e : 00000000`0000000a 00000000`0000000a 00000000`00000000 00000000`00000000 : WindowsTerminal+0x69c5 00000015`524ffa80 00007ff7`f409bf72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0x878e 00000015`524ffc40 00007ff8`3c8854e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal+0xbf72 00000015`524ffc80 00007ff8`3dba485b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x10 00000015`524ffcb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b SYMBOL_NAME: ucrtbase!abort+4e MODULE_NAME: ucrtbase IMAGE_NAME: ucrtbase.dll STACK_COMMAND: ~0s ; .ecxr ; kb FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 10.0.22000.1 FAILURE_ID_HASH: {e31753ac-c98a-8055-3663-47e707543d20} Followup: MachineOwner --------- ```
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-DefApp In-PR 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#15931
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?