title: How to Test for Memory Leaks?
body: <p>We have an application with hundreds of possible user actions, and think about how enhancing memory leak testing.</p>
  
  <p>Currently, here's the way it happens: When manually testing the software, if it appears that our application consumes too much memory, we use a memory tool, find the cause and fix it. It's a rather slow and not efficient process: the problems are discovered late and it relies on the good will of one developer.</p>
  
  <p>How can we improve that?</p>
  
  <ul>
  <li>Internally check that some actions (like "close file") do recover some memory and log it?</li>
  <li>Assert on memory state inside our unit tests (but it seems this would be a tedious task) ?</li>
  <li>Manually regularly check it from time to time?</li>
  <li>Include that check each time a new user story is implemented?</li>
  </ul>