WindowsAppSDK: Windows App Sdk 1.3 is not stable and might cause fail fast in Diagnostics::GetRuntimeElement

Describe the bug

KernelBase.dll!RaiseFailFastException()
combase.dll!RoFailFastWithErrorContextInternal2(HRESULT hrError, unsigned long cStowedExceptions, _STOWED_EXCEPTION_INFORMATION_V2 * * aStowedExceptionPointers) Line 1468
	at onecore\com\combase\winrt\error\error.cpp(1468)
Microsoft.ui.xaml.dll!Diagnostics::GetRuntimeElement(struct IInspectable *,class std::shared_ptr<class Diagnostics::RuntimeObject>)
Microsoft.ui.xaml.dll!XamlDiagnostics::GiveRootsToCallback(class Microsoft::WRL::ComPtr<struct IVisualTreeServiceCallback> const &)
Microsoft.ui.xaml.dll!std::_Func_impl_no_alloc<`XamlDiagnostics::AdviseVisualTreeChange'::`2'::<lambda_1>,long>::_Do_call()
Microsoft.ui.xaml.dll!Microsoft::WRL::Details::DelegateArgTraits<long (__cdecl ABI::Microsoft::UI::Dispatching::IDispatcherQueueHandler::*)(void)>::DelegateInvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,ABI::Microsoft::UI::Dispatching::IDispatcherQueueHandler,Microsoft::WRL::FtmBase>,`Advising::RunOnUIThread'::`2'::<lambda_1> &,1>::Invoke()
CoreMessagingXP.dll!Microsoft::UI::Dispatching::DispatcherQueue::DeferInvokeCallback(void *)
CoreMessagingXP.dll!CFlat::SehSafe::Execute<<lambda_a81ff790741c2a62f2197c2561f5fe49>>()
CoreMessagingXP.dll!Microsoft::CoreUI::ActionCallback::ImportAdapter$(class CFlat::Box$1<struct CFlat::FunctionPointerAndUserData$1<long > > *)
CoreMessagingXP.dll!Microsoft::CoreUI::Messaging::MessageSession::Callback_InvokeDeferInvoke(class Microsoft::CoreUI::ActionCallback *,struct System::UIntPtr)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::DeferredCall::Callback_Dispatch(void)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::DeferredCallDispatcher::Callback_OnDispatch(void)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::Dispatcher::Callback_DispatchNextItem(class Microsoft::CoreUI::Dispatch::DispatchItem *)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::Dispatcher::Callback_DispatchLoop(enum Microsoft::CoreUI::Dispatch::RunnablePriorityMask)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop(enum Microsoft::CoreUI::Dispatch::RunMode)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::UserAdapter::DrainCoreMessagingQueue(enum Microsoft::CoreUI::Dispatch::UserAdapter$UserPriority,void * *)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch(bool,enum Microsoft::CoreUI::Dispatch::UserAdapter$UserPriority,void * *)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatchRaw(enum Microsoft::CoreUI::Dispatch::UserAdapter$UserPriority,bool,void * *)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::UserAdapter::DoWork(struct HWND__ *,enum Microsoft::CoreUI::Dispatch::UserAdapter$UserPriority,bool)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::UserAdapter::HandleDispatchNotifyMessage(struct HWND__ *,unsigned __int64,__int64)
CoreMessagingXP.dll!Microsoft::CoreUI::Dispatch::UserAdapter::WindowProc(struct HWND__ *,unsigned int,unsigned __int64,__int64)

Error message:

Unhandled exception at 0x00007FFBFBDDE488 (Microsoft.ui.xaml.dll) in MyApp.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x0000021B6B77ACA0, 0x0000000000000002).

Steps to reproduce the bug

Unknown but Windows App Sdk 1.2 is much stable than 1.3

Expected behavior

No response

Screenshots

No response

NuGet package version

Windows App SDK 1.3.0: 1.3.230331000

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 22H2 (22621, 2022 Update)

IDE

Visual Studio 2022

Additional context

No response

About this issue

Original URL
State: open
Created a year ago
Comments: 21 (4 by maintainers)

Most upvoted comments

@wbokkers Thanks Wim - appreciate your response as well. We could be completely off the scent here, just going on the screen shot call stack. If so, we’ll course correct and take it from there.

Scottj1s on May 22, 2023

In 1.3.1, we fixed the top crash cause (a bug with System Backgrounds) and there is one more top hitter that appears to be an application bug since it only appears in a single application (we’ve reached out to the 3rd party developer). If you are seeing a different crash from this issue (specific to Diagnostics), please file a new issue and include a repro app (preferred), a crash dump, or (at the very least) a call stack. That will help us immensely. Thanks!

bpulliam on May 15, 2023