Note that there are some explanatory texts on larger screens.

plurals
  1. POWPF DropShadowEffect and Blur memory leaks
    primarykey
    data
    text
    <p>I'm writing an app, which is essentially a bunch of loose xaml screens - no codebehind, just dynamically linked to a ViewModel at runtime.</p> <p>When running this over a weekend on an older pc, there was a crash. Tracing and recreating showed there was a memory leak in igdumd32.dll (An intel graphics driver dll). After a bit of investigation I wrote 2 simple standalone apps with a very simple animation in centre screen. 1 with no effects and 1 with a dropshadoweffect on the animation - no other changes, literally a 1 line change to the first app (xaml is quite verbose, otherwise I'd post it here). I ran these through redgate's memory profiler tool for 40 minutes. The 1st one was fine: <img src="https://i.stack.imgur.com/ptXCV.png" alt="enter image description here"> but the 2nd one had a notable memory leak on igdumd32.dll and memory allocated by managed code:<img src="https://i.stack.imgur.com/l5te4.png" alt="enter image description here"> </p> <p>Another thing I noticed is that this doesn't happen on a new pc. Looking at the versions of igdumd32.dll - the older pc has a 2009 version (8.15.10.1930) whereas the newer (working) pc has the 2012 version (8.15.10.2639). </p> <p>Has anyone else experienced this? My thoughts are to only use special effects in xaml when the chipsets/drivers can handle this, but I can't find anything on the web or on MSDN that tells me hardware or driver limitations for these effects (beyond telling me that Hardware Acceleration is required for them or my CPU will bump up). </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload