Opening the snippets pane (from command palette) on settings window closes terminal

[garrgar]

Windows Terminal version

1.24.2812.0

Windows build number

10.0.26200.6901

Other Software

No response

Steps to reproduce

Open Terminal.
Select Settings from menu
Selecct "Command Palette" from menu
Click on "Open Snippets Pane"

Expected Behavior

Nothing, because that's the behaviour in release v1.23.12811.0

Actual Behavior

Terminal closes, silently.

[garrgar]

Now reported in Feedback Hub, and I supplied a link to this issue.

.dmp files available, request if wanted.

[lhecker]

(3f8c.2514): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
TerminalApp!winrt::impl::consume_Windows_Foundation_Collections_IVector<winrt::Windows::Foundation::Collections::IObservableVector<winrt::TerminalApp::FilteredTask>,winrt::TerminalApp::FilteredTask>::Clear+0xa0 [inlined in TerminalApp!winrt::TerminalApp::implementation::SnippetsPaneContent::UpdateSettings$_ResumeCoro$1+0x635]:
00007ff9`605effd5 488b08          mov     rcx,qword ptr [rax] ds:00000000`00000000=????????????????
0:000> kc
 # Call Site
00 TerminalApp!winrt::impl::consume_Windows_Foundation_Collections_IVector<winrt::Windows::Foundation::Collections::IObservableVector<winrt::TerminalApp::FilteredTask>,winrt::TerminalApp::FilteredTask>::Clear
01 TerminalApp!winrt::TerminalApp::implementation::SnippetsPaneContent::UpdateSettings$_ResumeCoro$1
02 TerminalApp!std::coroutine_handle<void>::resume
03 TerminalApp!wil::details::dispatcher_handler::Complete
04 TerminalApp!wil::details::dispatcher_handler::operator()
05 TerminalApp!winrt::impl::delegate<winrt::Windows::UI::Core::DispatchedHandler,wil::details::dispatcher_handler>::Invoke
06 Windows_UI!Windows::UI::Core::CDispatcher::InvokeAndCompleteItem
07 Windows_UI!Windows::UI::Core::CDispatcher::EnqueueAsyncWork::__l16::<lambda_980f345bc6e4ac8a906323c24a5fe9b1>::operator()
08 Windows_UI!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl Windows::System::IDispatcherQueueHandler::*)(void)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::System::IDispatcherQueueHandler,Microsoft::WRL::FtmBase>,<lambda_980f345bc6e4ac8a906323c24a5fe9b1>,-1>::Invoke
09 CoreMessaging!Windows::System::DispatcherQueue::DeferInvokeCallback
0a CoreMessaging!Microsoft::CoreUI::Dispatch::TimeoutHandler::ImportAdapter$::__l2::<lambda_654db17c35df07198786f0867aa10de6>::operator()
0b CoreMessaging!CFlat::SehSafe::Execute<<lambda_654db17c35df07198786f0867aa10de6> >
0c CoreMessaging!Microsoft::CoreUI::ActionCallback::ImportAdapter$
0d CoreMessaging!CFlat::DelegateImpl<Microsoft::CoreUI::ActionCallback,0,void __cdecl(void),long __cdecl(void *),0>::Invoke
0e CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCall::Callback_Dispatch
0f CoreMessaging!Microsoft::CoreUI::Dispatch::DeferredCallDispatcher::Callback_OnDispatch
10 CoreMessaging!Microsoft::CoreUI::Dispatch::Dispatcher::Callback_DispatchNextItem
11 CoreMessaging!Microsoft::CoreUI::Dispatch::Dispatcher::Callback_DispatchLoop
12 CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop
13 CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::DrainCoreMessagingQueue
14 CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch
15 CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatchRaw
16 CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::DoWork
17 CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::WindowProc
18 user32!UserCallWinProcCheckWow
19 user32!DispatchClientMessage
1a user32!__fnDWORD
1b ntdll!KiUserCallbackDispatcherContinue
1c win32u!ZwUserGetMessage
1d user32!GetMessageW
1e WindowsTerminal!WindowEmperor::HandleCommandlineArgs
1f WindowsTerminal!wWinMain
20 WindowsTerminal!invoke_main
21 WindowsTerminal!__scrt_common_main_seh
22 KERNEL32!BaseThreadInitThunk
23 ntdll!RtlUserThreadStart

[zadjii-msft]

I could have swore there was a dupe for this.

Bet we're just assuming there's an

yep okay he's on it