title: Using Charles Debugging with Chrome gives me 1-3% "Connection timed out"
body: <p>At my job, we use the debugging tool Charles Proxy a lot. So I always have it running in the background. Sometimes it's recording, other times it's not.<br>
  However, lately it has started acting up. For every web request I do, there is a 1-3% chance that it will fail to connect with the reason: "Connect: Connection timed out: connect"</p>
  
  <p><br>
  <b>Test case</b><br>
  I did a test with Charles: Use the 'repeat advanced' option on a file to fetch it 50 times:
  <img src="https://i.stack.imgur.com/QiZa3.png" alt="Two of the 50 requests failed">
  <br></p>
  
  <p>As you can see, 2 of them failed. (And it took it 21 seconds to timeout). The 98 other times, it took ~4ms to complete the request.</p>
  
  <p>I did the same test with Charles closed and Fiddler opened instead.<br>
  After 400 requests of the file, not a single one had failed.</p>
  
  <p><b>Happens on normal usage</b><br>
  Here, it happened when I opened the company game site. A rather important request failed and thus, the site never fully loaded.
  <img src="https://i.stack.imgur.com/YjuCf.png" alt="enter image description here"></p>
  
  <p><b>I have tried</b><br>
  I tried restarting my computer.<br>
  I tried updating to the newest version of Charles.<br>
  I tried uninstalling and installing Charles.<br>
  I tried disconnecting from the VPN we're on.<br></p>
  
  <p>I tried closing down Charles and that seems to fix it. But I need to have Charles running and I don't want to open and close it all the time.<br>
  I tried using Firefox instead of Chrome and it seemed to happen very rarely or almost never. However Firefox is really bad to use when working with Flash.</p>
  
  <p><strong>Edit (Chrome net-internals)</strong><br>
  I logged the output from <code>chrome://net-internals/#events</code> when trying to load a file that failed.
  Pastebin dumps: <code>http://pastebin.com/dgMaLMKc</code> then <code>http://pastebin.com/dAGpJCJy</code></p>