title: OkHttp: avoid leaked connection warning
body: <p>I am using OkHttp 3, and I keep getting leaked connection warnings:</p>
  
  <pre><code>WARNING: A connection to https://help.helpling.com/ was leaked. Did you forget to close a response body?
  Jul 14, 2016 6:57:09 PM okhttp3.ConnectionPool pruneAndGetAllocationCount
  </code></pre>
  
  <p>Everytime I get a <code>ResponseBody</code>, I either call <code>.string()</code> which supposedly closes the stream for me, or I explicitly close it in a <code>finally</code> block, in the following way:</p>
  
  <pre><code>ResponseBody responseBody = response.body();
  try (Reader responseReader = responseBody.charStream()) {
      ...
  }
  finally {
      responseBody.close();
  }
  </code></pre>
  
  <p>My application makes intense use of the network, and yet that warning appears frequently. I never observed any problem caused by this presumed leak, but I would still like to understand <em>if</em> and <em>what</em> I am doing wrong.</p>
  
  <p>Could anyone shed some light on this?</p>