Windows terminal crash

[NeilMacMullen]

Windows Terminal version

1.18.3181.0

Windows build number

10.0.22631.0

Other Software

Custom application

Steps to reproduce

Unclear - still under investigation. Possible that application is experiencing OOM exception or generating large amounts or console output

Expected Behavior

Application should be terminated but terminal should keep running

Actual Behavior

We use Windows Terminal to spawn a number of powershell scripts in separate terminal processes. (The "master" script that does this simply invokes... Start-Process -windowstyle normal powershell -ArgumentList $arglist)

The poweshell scripts run some custom CLI commands periodically (i.e. they run the command then sleep for a few hours).

This results in a number of tiled windows....

Recently we have found instances where Terminal appears to crash in a way that the entire process is killed - i.e,. all spawned windows disappear. The trigger appears to be a fault in one of the CLI applications (possibly out-of-memory) but we would expect the behaviour in this case for the application to be killed, not the entire Terminal process. (Happy to close though if this is "expected" behaviour.)

Unfortunately we don't have a lot of post-mortem information at this time... EventLog shows an Application Error for Terminal...

Faulting application name: WindowsTerminal.exe, version: 1.18.2311.14001, time stamp: 0x6553b19e
Faulting module name: ntdll.dll, version: 10.0.22621.2506, time stamp: 0xbced4b82
Exception code: 0xc0000409
Fault offset: 0x00000000000a7d18
Faulting process ID: 0x0x5714
Faulting application start time: 0x0x1DA491FE3458FB2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 2082cf3e-3952-4061-bfe1-e6bc7aa7bef6
Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App