Application crash on WinUITap.dll

[NandishNR]

Describe the bug

Faulting application name: JioMeet.exe, version: 4.23.2.12, time stamp: 0x63558578
Faulting module name: Microsoft.VisualStudio.DesignTools.WinUITap.dll, version: 17.0.33006.217, time stamp: 0x633f5715
Exception code: 0xc0000005
Fault offset: 0x0000000000069631
Faulting process id: 0x63c8
Faulting application start time: 0x01d96623b481d77d
Faulting application path: C:\Users\nandish.nr\source\repos\Jio-WinUI3\src\JMB\JMB\bin\x64\Debug\net6.0-windows10.0.19041.0\win10-x64\JioMeet.exe
Faulting module path: c:\program files\microsoft visual studio\2022\community\common7\ide\commonextensions\microsoft\xamldiagnostics\x64\WinUI3\Microsoft.VisualStudio.DesignTools.WinUITap.dll
Report Id: 93777858-7dfd-481c-b544-7e2af14559a1
Faulting package full name:
Faulting package-relative application ID:

Steps to reproduce the bug

Launch application and navigate between screen, application will go to busy state and crash

Expected behavior

No response

Screenshots

No response

NuGet package version

None

Windows version

No response

Additional context

No response

[kondareddy]

in .NET we can always get stack trace of the exception so that we can fix easily but in WinUI +.NET 6 - generic details are seen in event viewer and crash dump analysis as well.

are we missing something here?

[bpulliam]

Duplicate of #8806

[JochemPalmsens]

@bpulliam but that issue has also been closed and it's not clear what's the referring issue now.

[codendone]

Clarity on the fix has now been added in that other issue.

[JochemPalmsens]

@codendone it's not fixed. Please reopen either this or the other issue. See our experiences in that other issue.

[codendone]

@JochemPalmsens Thanks for the ping. Investigation has resumed for #8806. Let's use that issue for tracking.