Skip to content
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 at 0x21792849 (threadpoolwinrt.dll) 0xC0000005: Access violation reading location 0x00000000. #2712

Closed
shyamshr93 opened this issue Jul 6, 2022 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@shyamshr93
Copy link

Describe the bug

Closing the app while it is running and deployed from Visual Studio gives this exception. Only happens in version Windows App SDK 1.1 and after.

Steps to reproduce the bug

  1. Create a packaged Windows App SDK app (1.1 and above).
  2. Run the app from Visual Studio.
  3. Just close the app (not from visual studio "stop debug" button ).

Expected behavior

No exception should be given.

Screenshots

image

NuGet package version

1.1.2

Packaging type

Packaged (MSIX)

Windows version

Windows 10 version 21H2 (19044, November 2021 Update)

IDE

Visual Studio 2022

Additional context

No response

@manodasanW
Copy link
Member

@shyamshr93 are you still able to repro this issue? I tried your repro steps with a blank app on the OS version you mentioned but haven't been able to repro it. If you are still able to repro it, can you confirm whether you see it with a blank app or just in your app? And are you able to provide what you see under call stack in Visual Studio when you hit this?

@shyamshr93
Copy link
Author

@manodasanW yes it is still happening in latest version (1.1.4) too as you can see below. My app has multiple webview2 if that can help.
image

@codendone
Copy link
Contributor

@shyamshr93 The threadpoolwinrt.pdb in your screenshot and your mention of WebView2 suggests you're seeing microsoft/microsoft-ui-xaml#7260. If you call Close() on the WebView2 elements before the app closes, hopefully that should workaround the issue.

@shyamshr93
Copy link
Author

@codendone dotnet/maui#7317 (comment) this workaround seems to have fix the issue. I can't reproduce the bug now.

@codendone
Copy link
Contributor

Excellent! Please use that workaround for now. You can track the issue I mentioned for when this gets fixed in the platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants