App with WindowsAppSDK 1.7.X will crash after "IDispatcherQueueHandler::Invoke failed"

[zhuxb711]

Describe the bug

After upgrading my application to WindowsAppSDK 1.7.X, sometimes I would notice that a log print out IDispatcherQueueHandler::Invoke failed! and then the App crashed.

Still don't know what trigger that, it seems a random crash. Just note here in case anyone meet the same issue.

Steps to reproduce the bug

Don't know how to trigger that. And could not provide the stack trace because Microsoft.ui.xaml.pdb is missing from Microsoft Symbol Server and could not be loaded

Expected behavior

No response

Screenshots

No response

NuGet package version

Windows App SDK 1.7.1: 1.7.250401001

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 24H2 (22621, October 2024 Update)

IDE

Visual Studio 2022

Additional context

No response

[RDMacLachlan]

Hi @zhuxb711,

This failure means that some DispatcherQueue handler failed. Try setting the debugger to break in on native exceptions. If this is a C# app, you might also need to breakpoint on C# apps. Hopefully these can catch what is failing, providing you the source location or a better callstack of the failure.

If that doesn't work, can you provide a sample repro project?

[zhuxb711]

Hi @zhuxb711,

This failure means that some DispatcherQueue handler failed. Try setting the debugger to break in on native exceptions. If this is a C# app, you might also need to breakpoint on C# apps. Hopefully these can catch what is failing, providing you the source location or a better callstack of the failure.

If that doesn't work, can you provide a sample repro project?

Thanks, but what actually is DispatcherQueue handler？It's C# app, break on native exception means break on win32 c++ exception?

[lhak]

I think this issue might be related to microsoft/microsoft-ui-xaml#10447 as I see the same error message when the unhandled exception handler is supposed to be invoked (which does not happen). It looks like appsdk 1.7 has broken some of the exception handling for c# apps.

[lhak]

So the issue seems to be caused by a change in the DispatcherQueueSynchronizationContext class (as described in the issue linked above).

[RDMacLachlan]

The following Issue #10447 in the Microsoft/Microsoft-UI-XAML is being used to track this issue. Closing this issue as a duplicate.

And recommending:

This failure means that some DispatcherQueue handler failed. Try setting the debugger to break in on native exceptions. If this is a C# app, you might also need to breakpoint on C# apps. Hopefully these can catch what is failing, providing you the source location or a better callstack of the failure.

If that doesn't work, can you provide a sample repro project?