-
Notifications
You must be signed in to change notification settings - Fork 692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception thrown by minimal program #6817
Labels
duplicate
This issue or pull request already exists
Comments
WinUI throws native exceptions constantly, including at app launch, app close, and when interacting with various controls such as opening drop downs. The team is aware of this, but since the exceptions don't impact program execution I doubt that the situation will change. |
ojhad
added
duplicate
This issue or pull request already exists
and removed
needs-triage
Issue needs to be triaged by the area owners
labels
Mar 14, 2022
Marking as duplicate of: #6352 |
Work with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Exception thrown at 0x76C4B922 (KernelBase.dll) in TestApp2.exe: WinRT originate error - 0x80000013 : 'The given object has already been closed / disposed and may no longer be used.'.
The exception is received when a minimal program is exited.
Steps to reproduce the bug
Install VS 2022 Community Edition with WIndowsAppSDK.
Create a test solution using the "Blank App, Packaged (WinUI 3 in Desktop)" template. In the NuGet package manager observe Microsoft.Windows.SDK.BuildTools 10.0.22000.194 and Microsoft.WindowsAppSDK 1.0.0.
In the Exceptions Setting window, select all the exceptions.
Compile and run. No need to click the button. Exit by clicking the "X" and observe the exception cited above.
There are also other exceptions in the Output/Immediate window as copied under "Screenshots" below.
Expected behavior
No exceptions at all!
Screenshots
*Output window: *
Immediate window:
NuGet package version
No response
Windows app type
Device form factor
No response
Windows version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: