Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Access Violation and app crash when trying to debug Application.Current
See original GitHub issueDescribe the bug
I noticed that my app was crashing when trying to read the resources from a background thread:
var res = Application.Current?.Resources
I don’t actually want to start using things, but rather I wanted to get the dispatcher queue and then enqueue a delegate to update the dictionary. But, it appears just reading this crashes the app and also adding Application.Current in the IDE’s debug intermediate window also throws.
Steps to reproduce the bug
On a background thread:
var res = Application.Current?.Resources
Expected behavior
No crash and the resource dictionary is readable.
Screenshots
No response
NuGet package version
1.0.0
Packaging type
Packaged (MSIX)
Windows version
Windows 11 version 21H2 (22000)
IDE
Visual Studio 2022-preview
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
In the meantime, the best practice is to store away a copy of the DispatcherQueue somewhere in an app global.
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.