title: Troubleshooting native memory leaks in Windows Store applications using DebugDiag and LeakTrack
body: <p>The scenario is pretty simple:</p>
  
  <p>I have a memory leak in a Windows Store App, identified as native after using dotMemory profiler. Since this tool is limited to analyzing managed memory I did further research by performing a memory dump analysis using DebugDiag. 
  This got me one step further and I could find that the increasing memory is committed to a heap used by mscoreei (anyone has additional info about this dll? A simple google search does not return much)</p>
  
  <p>DebugDiag also has a nice feature called Memory Leak analysis witch injects the LeakTrack.dll into a running process to collect information about memory allocation, which in turn potentially can help identify which parts of managed code use the native leaking resource. However, I am getting an error when I try use this on my Windows Store App</p>
  
  <p>"<strong>Failed to monitor for leaks in process .... Please make sure that everyone has read and execute permissions for ...\LeakTrack.dll</strong>".</p>
  
  <p>I did modify the permissions to that file so everyone has full access, but still the same error.</p>
  
  <p>My questions are:</p>
  
  <p>How can I use LeakTrack on a Windows Store Apps?</p>
  
  <p>What is the the best/alternative approach to perform native memory leaks in Windows Store Apps?</p>