G
Guest
Hi,
I've been profiling a WPF application using Frame objects to navigate
between screens implemented as pages. Using two different profilers I see
that BitmapSourceSafeMILHandles are never disposed even though there are no
live references to them (that I can tell). These objects are not explicitly
created by me and by the call stacks I assume they are part of the rendering
process. The number of undisposed instances grows even if a navigate back
and forth between the same two pages.
Looking deeper at my profiling results the undisposed instances of
BitmapSourceSafeMILHandle have a variable named __gcPressure with a value of
0. That probably explains why they are never disposed. Regardless it is
strange how I could build up over a million of these guys (I set up an
automated test) without a single instance being disposed. Is this a memory
leak?
-alberto
I've been profiling a WPF application using Frame objects to navigate
between screens implemented as pages. Using two different profilers I see
that BitmapSourceSafeMILHandles are never disposed even though there are no
live references to them (that I can tell). These objects are not explicitly
created by me and by the call stacks I assume they are part of the rendering
process. The number of undisposed instances grows even if a navigate back
and forth between the same two pages.
Looking deeper at my profiling results the undisposed instances of
BitmapSourceSafeMILHandle have a variable named __gcPressure with a value of
0. That probably explains why they are never disposed. Regardless it is
strange how I could build up over a million of these guys (I set up an
automated test) without a single instance being disposed. Is this a memory
leak?
-alberto