[Problem/Bug]: Crash in embedded_browser_webview_current::internal::ClientWindowCoreInput::Close

What happened?

We've deployed WebView2 in a popular UWP app on Microsoft Store.
Recent crash reports from Partner Center have shown about 40% of stacktraces (about 4000 incidents) are related to embedded_browser_webview_current::internal::ClientWindowCoreInput::Close, exception code is C0000005:

Frame	Image	Function	Offset	
"0"	"EmbeddedBrowserWebView.dll"	"embedded_browser_webview_current::internal::ClientWindowCoreInput::SubclassWndProc"	"0x0000000000000043"	
"1"	"EmbeddedBrowserWebView.dll"	"embedded_browser_webview_current::internal::ClientWindowCoreInput::StaticSubclassWndProc"	"0x0000000000000040"	
"2"	"comctl32.dll"	"CallNextSubclassProc"	"0x0000000000000069"	
"3"	"comctl32.dll"	"MasterSubclassProc"	"0x000000000000008B"	
"4"	"user32.dll"	"_InternalCallWinProc"	"0x000000000000002B"	
"5"	"user32.dll"	"UserCallWinProcCheckWow"	"0x000000000000023A"	
"6"	"user32.dll"	"DispatchClientMessage"	"0x00000000000000AF"	
"7"	"user32.dll"	"__fnDWORD"	"0x0000000000000035"	
"8"	"ntdll.dll"	"KiUserCallbackDispatcher"	"0x000000000000004D"	
"9"	"win32u.dll"	"NtUserDestroyWindow"	"0x000000000000000A"	
"10"	"Windows.UI.dll"	"Windows::UI::Core::CCoreInput_&RuntimeClass_Windows_UI_Core_CoreComponentInputSource_::Cleanup"	"0x00000000000000B7"	
"11"	"Windows.UI.dll"	"Windows::UI::Core::CCoreInput_&RuntimeClass_Windows_UI_Core_CoreComponentInputSource_::~CCoreInput_&RuntimeClass_Windows_UI_Core_CoreComponentInputSource_"	"0x0000000000000100"	
"12"	"Windows.UI.dll"	"Windows::UI::Core::CCoreInput_&RuntimeClass_Windows_UI_Core_CoreComponentInputSource_::`scalar deleting destructor'"	"0x000000000000000D"	
"13"	"Windows.UI.dll"	"Windows::UI::Core::CCoreInput_&RuntimeClass_Windows_UI_Core_CoreComponentInputSource_::Release"	"0x000000000000006A"	
"14"	"EmbeddedBrowserWebView.dll"	"embedded_browser_webview_current::internal::ClientWindowCoreInput::Close"	"0x000000000000014D"	
"15"	"EmbeddedBrowserWebView.dll"	"embedded_browser_webview_current::Controller::CloseInternal"	"0x00000000000001A7"	
"16"	"EmbeddedBrowserWebView.dll"	"embedded_browser_webview_current::EmbeddedBrowserWebView::CloseInternal"	"0x00000000000002A2"	
"17"	"EmbeddedBrowserWebView.dll"	"base::internal::Invoker_base::internal::BindState_void (embedded_browser_webview_current::EmbeddedBrowserWebView::*)(long, bool, embedded_browser_webview::WebViewCloseReason) __attribute__((thiscall)),base::internal::RetainedRefWrapper_embedded_browser_we"	"0x0000000000000038"	
"18"	"EmbeddedBrowserWebView.dll"	"base::TaskAnnotator::RunTaskImpl"	"0x0000000000000126"	
"19"	"EmbeddedBrowserWebView.dll"	"base::TaskAnnotator::RunTask__"	"0x0000000000000033"	
"20"	"EmbeddedBrowserWebView.dll"	"embedded_browser_webview::internal::AppTaskRunner::DoWork"	"0x0000000000000136"	
"21"	"EmbeddedBrowserWebView.dll"	"embedded_browser_webview::internal::AppTaskRunner::MessageCallback"	"0x0000000000000019"	
"22"	"EmbeddedBrowserWebView.dll"	"base::internal::Invoker_base::internal::BindState_bool (embedded_browser_webview::internal::AppTaskRunner::*)(unsigned int, unsigned int, long, long *) __attribute__((thiscall)),base::internal::UnretainedWrapper_embedded_browser_webview::internal::AppTask"	"0x0000000000000034"	
"23"	"EmbeddedBrowserWebView.dll"	"base::win::MessageWindow::WindowProc"	"0x00000000000001BA"	
"24"	"EmbeddedBrowserWebView.dll"	"base::win::WrappedWindowProc_&base::win::MessageWindow::WindowProc_"	"0x0000000000000048"	
"25"	"user32.dll"	"_InternalCallWinProc"	"0x000000000000002B"	
"26"	"user32.dll"	"UserCallWinProcCheckWow"	"0x000000000000023A"	
"27"	"user32.dll"	"DispatchMessageWorker"	"0x00000000000001B6"	
"28"	"user32.dll"	"DispatchMessageW"	"0x0000000000000010"	
"29"	"Windows.UI.dll"	"Windows::UI::Core::CDispatcher::ProcessMessage"	"0x0000000000000105"	
"30"	"Windows.UI.dll"	"Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal"	"0x000000000000009D"	
"31"	"Windows.UI.dll"	"Windows::UI::Core::CDispatcher::WaitAndProcessMessages"	"0x000000000000002D"	
"32"	"twinapi.appcore.dll"	"Event::WaitAndProcessEvents"	"0x0000000000000063"	
"33"	"twinapi.appcore.dll"	"Windows::ApplicationModel::SuspendingOperation::WaitForAnyOutstandingDeferrals"	"0x0000000000000024"	
"34"	"twinapi.appcore.dll"	"Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume"	"0x000000000000012D"	
"35"	"twinapi.appcore.dll"	"Windows::ApplicationModel::Core::CoreApplicationView::SuspendResumeHandler::Invoke"	"0x00000000000000BD"	
"36"	"Windows.UI.dll"	"Windows::UI::Core::CDispatcher::ProcessInvokeItem"	"0x00000000000003EC"	
"37"	"Windows.UI.dll"	"Windows::UI::Core::CDispatcher::ProcessMessage"	"0x000000000000017D"	
"38"	"Windows.UI.dll"	"Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal"	"0x000000000000009D"	
"39"	"Windows.UI.dll"	"Windows::UI::Core::CDispatcher::ProcessEvents"	"0x0000000000000065"	
"40"	"Windows.UI.Xaml.dll"	"DirectUI::FrameworkView::Run"	"0x000000000000008C"	
"41"	"twinapi.appcore.dll"	"Windows::ApplicationModel::Core::CoreApplicationView::Run"	"0x0000000000000032"	
"42"	"twinapi.appcore.dll"	"_lambda_a740d69e4550265529206848c8e72a27_::_lambda_invoker_stdcall_"	"0x000000000000008B"	
"43"	"SHCore.dll"	"_WrapperThreadProc"	"0x00000000000000E0"	
"44"	"kernel32.dll"	"BaseThreadInitThunk"	"0x0000000000000019"	
"45"	"ntdll.dll"	"__RtlUserThreadStart"	"0x000000000000002B"	
"46"	"ntdll.dll"	"_RtlUserThreadStart"	"0x000000000000001B"	

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

No response

SDK Version

1.0.1722.45

Framework

WinUI2/UWP

Operating System

Windows 10, Windows 11

OS Version

No response

Repro steps

Suspend/Resume the app?

Repros in Edge Browser

No

Regression

Don't know

Last working version (if regression)

No response

AB#45884664

Start with the reported Suspend/Resume path in the stack trace, especially ClientWindowCoreInput::Close, Controller::CloseInternal, and EmbeddedBrowserWebView::CloseInternal. Review the WebView2 SDK version 1.0.1722.45 behavior on WinUI2/UWP across Windows 10 and 11, then establish a reproducible suspend/resume case and confirm that the access-violation crash no longer occurs.