NicholasChrzan
NicholasChrzan
We are seeing this issue in our Win App SDK 1.4 and 1.6 based applications in already installed applications. It started showing up around 3-4 days ago. I'm guessing there...
@champnic If you look above this bug was also flagged in a Delphi implementation, so it's a fairly safe to assume that this is happening outside of the Windows App...
We're still seeing Pointer messages being randomly generated as well even after upgrading to 1.8.0. We suspect it has to do with this issue because flyouts and popups are not...
The only way I've found to have things clean up properly is to explicitly unwire all event handlers (including ones specified in the XAML) while either the appwindow is destroying...
@steam3d If you look at @akainth015 post above mine he has a link to a simple project which illustrates the memory leak. If you profile it with a memory profiler...
@steam3d If you care about it being released don't use x:Bind just use the older Binding nomenclature and it will clean up.
One thing I've found that if you follow the WinRT/UWP approach of a single window and frame on navigating around (while flushing history) the UI elements clean up as expect....