title: Visual Studio Diagnostics stops with errors
body: <p>I'm trying debug memory usage of a 32 bit C++ native application using the Visual Studio Diagnostics tools.<br />
  This application is running for about 5 minutes and consumes (at its peak) more than 3Gb of RAM.<br />
  When using the Visual Studio Diagnostics to profile RAM, the application runs correctly (although much slower). I'm taking a few snapshots while it is running.<br />
  <strong>When it terminates and I get the following error:</strong></p>
  <blockquote>
  <p>Diagnostics session stopped with errors.</p>
  <p>There is not enough space on the disk.</p>
  </blockquote>
  <p>No diagnostics are displayed.</p>
  <h3>But there is enough space on the disk (~40Gb).</h3>
  <p>I thought of attaching to a running process, take a snapshot and detach. However, I couldn't see how to profile RAM by attaching to a running process. I was only able to profile CPU. I'm not sure RAM profiling is supported when attaching to process.</p>
  <p>Did anyone see this problem before? Any idea how to work around this?</p>
  <hr />
  <h1>Update</h1>
  <p>Eventually I got the data I needed using <a href="https://msdn.microsoft.com/en-us/library/windows/hardware/ff558947(v=vs.85).aspx" rel="nofollow noreferrer">UMDH</a>.<br />
  UMDH did the job in a simple and straightforward way, while other tools (I tried &quot;Visual Studio Diagnostics&quot; and &quot;MTuner&quot;) failed miserably.</p>