title: Does jmap force garbage collection when the live option is used?
body: <p>I've been experimenting with <code>jmap -histo</code> and <code>jmap -dump</code> today</p>
  
  <p>When run in this sequence</p>
  
  <pre><code>jmap -dump:format=b,file=heap.1 [pid]
  jmap -dump:live,format=b,file=heap.2 [pid]
  jmap -dump:format=b,file=heap.3 [pid]
  </code></pre>
  
  <p><code>heap.3</code> resembles <code>heap.2</code> more than <code>heap.1</code>. In particular, the "dead" objects that I'm interested in in <code>heap.1</code> are absent from <code>heap.3</code>.</p>
  
  <p>Seeing this, I started looking for documentation that would tell me what I should expect.  The closest I managed to get was <a href="http://www.java.net/node/656376" rel="noreferrer">this discussion</a>, where the comments from briand and alanb imply that in practice I can expect this GC to occur when I use the live option; but the answers are five years old, and posts to a forum seem a bit informal for a specification.</p>
  
  <p>Where can I find the current behavior documented?</p>