[Preview] Windows Terminal crashes if settings tab is the last to be closed #18118

Open
opened 2026-01-31 06:04:12 +00:00 by claunia · 0 comments
Owner

Originally created by @ashemedai on GitHub (Aug 6, 2022).

Windows Terminal version

1.15.2002.0

Windows build number

10.0.19043.0

Other Software

Not relevant.

Steps to reproduce

Not a 100% reproducible case, but happens fairly often enough (90%?). There might be some unnecessary steps here, I tried to eliminate as many as possible. This is after a fresh install, no settings changed yet.

  1. Open Windows Terminal preview
  2. Open Settings
  3. Close tab with whatever the default profile is
  4. Only have the Settings tab left
  5. Select Defaults
  6. Scroll down so that the view pane with options is fully scrolled up (Appearance and Advanced are visible).
  7. (Unsure: might need to hover over Appearance and Advanced so that they have been lit up)
  8. Close Settings by clicking the x icon on the tab

Expected Behavior

Windows Terminal closes.

Actual Behavior

Windows Terminal crashes with an Unhandled exception thrown: read access violation. **_Right** was 0x23EA8E61000. First entry on the stack is Windows.UI.Xaml.dll!std::pair<void *,ctl::WeakRefPtr>::operator=<std::pair<void *,ctl::WeakRefPtr>,0>(std::pair<void *,ctl::WeakRefPtr> && _Right) Line 198, which is the destructor for AnimatedIcon() in AnimatedIcon.h

AnimatedIconProperties is shown as {...}.

Disassembly of the stack frame:

            int> = 0>
    constexpr pair(_Other1&& _Val1, _Other2&& _Val2) noexcept(
        is_nothrow_constructible_v<_Ty1, _Other1>&& is_nothrow_constructible_v<_Ty2, _Other2>) // strengthened
00007FFAFEFDDA86  mov         rax,qword ptr [rdx]

With:

Name Value
RBX 0000023EA8E60FF0
RCX 0000000000000000
RDX 0000000000000000
RDI 000000A67FEFE340

Event Viewer entry:

Faulting application name: WindowsTerminal.exe, version: 1.15.2207.19002, time stamp: 0x62d70c23
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.19041.1826, time stamp: 0x9fb9b996
Exception code: 0xc0000005
Fault offset: 0x000000000027da86
Faulting process ID: 0x3b54
Faulting application start time: 0x01d8a9a2e9c6033a
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.15.2002.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report ID: 55c5bf2e-3cf1-4d21-9ffc-8d2073ee7c83
Faulting package full name: Microsoft.WindowsTerminalPreview_1.15.2002.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I would love to give a Feedback Hub link, but Feedback Hub today suddenly decided that, when pressing Start recording: We couldn't start the recording. Please select Start recoding to try again. And given that no clear indication is given what is going on, I cannot do much to fix this.

Edit addendum: a quick animated GIF illustrating the problem:
steps

Originally created by @ashemedai on GitHub (Aug 6, 2022). ### Windows Terminal version 1.15.2002.0 ### Windows build number 10.0.19043.0 ### Other Software Not relevant. ### Steps to reproduce Not a 100% reproducible case, but happens fairly often enough (90%?). There might be some unnecessary steps here, I tried to eliminate as many as possible. This is after a fresh install, no settings changed yet. 1. Open Windows Terminal preview 2. Open Settings 3. Close tab with whatever the default profile is 4. Only have the Settings tab left 5. Select Defaults 6. Scroll down so that the view pane with options is fully scrolled up (Appearance and Advanced are visible). 7. (Unsure: might need to hover over Appearance and Advanced so that they have been lit up) 8. Close Settings by clicking the `x` icon on the tab ### Expected Behavior Windows Terminal closes. ### Actual Behavior Windows Terminal crashes with an `Unhandled exception thrown: read access violation. **_Right** was 0x23EA8E61000.` First entry on the stack is `Windows.UI.Xaml.dll!std::pair<void *,ctl::WeakRefPtr>::operator=<std::pair<void *,ctl::WeakRefPtr>,0>(std::pair<void *,ctl::WeakRefPtr> && _Right) Line 198`, which is the destructor for `AnimatedIcon()` in `AnimatedIcon.h` `AnimatedIconProperties` is shown as `{...}`. Disassembly of the stack frame: ``` int> = 0> constexpr pair(_Other1&& _Val1, _Other2&& _Val2) noexcept( is_nothrow_constructible_v<_Ty1, _Other1>&& is_nothrow_constructible_v<_Ty2, _Other2>) // strengthened 00007FFAFEFDDA86 mov rax,qword ptr [rdx] ``` With: | Name | Value | | ------ | ------ | | RBX | 0000023EA8E60FF0 | | RCX | 0000000000000000 | | RDX | 0000000000000000 | | RDI | 000000A67FEFE340 | Event Viewer entry: ``` Faulting application name: WindowsTerminal.exe, version: 1.15.2207.19002, time stamp: 0x62d70c23 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.19041.1826, time stamp: 0x9fb9b996 Exception code: 0xc0000005 Fault offset: 0x000000000027da86 Faulting process ID: 0x3b54 Faulting application start time: 0x01d8a9a2e9c6033a Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.15.2002.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report ID: 55c5bf2e-3cf1-4d21-9ffc-8d2073ee7c83 Faulting package full name: Microsoft.WindowsTerminalPreview_1.15.2002.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` I would love to give a Feedback Hub link, but Feedback Hub today suddenly decided that, when pressing Start recording: `We couldn't start the recording. Please select Start recoding to try again.` And given that no clear indication is given what is going on, I cannot do much to fix this. Edit addendum: a quick animated GIF illustrating the problem: ![steps](https://user-images.githubusercontent.com/610865/183254990-189cb27e-78b8-4f1e-8895-1d8f7fa1d10c.gif)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18118