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.
WPF memory leaks in navigation context
See original GitHub issueHello.
If WPF MapControl is located in a navigation context (i.e. Page within a Frame or UserControl in ContentControl) and user navigates back and forth between UserControls, the Controls that contain MapControl are not getting disposed of which leads to a memory leak. This happens even if I use the master branch. Quick memory debugging showed that it is related to TimerCallback - possibly relates to https://github.com/Mapsui/Mapsui/issues/1395 . What do you think of making the WPF MapControl IDisposable?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (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
@ondrasvoboda The automatic counting did not work for me, but since the
Disposemethod was madepublic, I decided to callDisposemanually. After that the leak was gone.This has been fixed.