title: A heap allocation was leaked, Application Verifier/ WinDbg
body: <p>I'm debugging an executable using Application Verifier and WinDbg. I have the "Leaks" test turned on under "Basics". My problem is that when Application Verifier finds a leak, it seems to enter some kind of exception-throwing infinite loop. I get an error like this:</p>
  
  <pre><code>=======================================
  VERIFIER STOP 0000000000000900: pid 0x1FE0: A heap allocation was leaked. 
  
      00000000155A6FF0 : Address of the leaked allocation. Run !heap -p -a &lt;address&gt; to get additional information about the allocation.
      0000000000571BE0 : Address to the allocation stack trace. Run dps &lt;address&gt; to view the allocation stack.
      0000000012314FD8 : Address of the owner dll name. Run du &lt;address&gt; to read the dll name.
      000007FEF8460000 : Base of the owner dll. Run .reload &lt;dll_name&gt; = &lt;address&gt; to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.
  
  
  =======================================
  </code></pre>
  
  <p>But when I press <code>F5</code>to continue debugging I get the exact same message again (and again and again), just with slightly different information for the addresses.</p>
  
  <p>Why is this happening? Is there a way to ignore this leak without turning off the leak checks entirely? As it stands, I can't run my program to completion to test for other issues because Application Verifier gets "hung up" on this leak.</p>