title: Ajax request pending forever on Chrome
body: <p>I have a random problem with Chrome (v60.0.3112.101 on Linux, but reproduced as well by end-users in production on other systems).
  There's a page that consists in a list of songs, and a click on any of them triggers an ajax request to fetch the file on the server (amongst other things).</p>
  
  <p>After a certain number of "clicks" (never the same number, never on the same file), the ajax request that is supposed to fetch resource is shown as "pending" forever (I've waited more than 30 minutes for it to finish).</p>
  
  <p><a href="https://i.stack.imgur.com/EHptQ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/EHptQ.png" alt="enter image description here"></a></p>
  
  <p>In the "Timing" tab of the developer tools panel, the request is shown as "stalled", and indeed, Nginx logs (we use  it as a reverse proxy) and the backend application itself show that the request never reaches the server.</p>
  
  <p><a href="https://i.stack.imgur.com/R5Lpt.png" rel="noreferrer"><img src="https://i.stack.imgur.com/R5Lpt.png" alt="enter image description here"></a></p>
  
  <p>I've tried several things with no success whatsoever:</p>
  
  <ul>
  <li>disabling the "prediction service to load pages quicker"</li>
  <li>add a random uuid on every request to make sure the cache is not used</li>
  <li>updating jquery and soundmanager2 (which is the library that starts the request)</li>
  <li>started Chrome with no extensions</li>
  </ul>
  
  <p>I also tried to re-run the request from the Developer Tools console, and it stays in a pending state as well.</p>
  
  <pre><code>url = "/api/download/songs/7969/28962/28962_original.mp3?download_key=81b285e61f7880a0a07a977dbc47b78a1d57e3690263a646da65a261957f979a&amp;r=" + Math.random();
  $.get(url);
  </code></pre>
  
  <p><a href="https://i.stack.imgur.com/2fesr.png" rel="noreferrer"><img src="https://i.stack.imgur.com/2fesr.png" alt="enter image description here"></a></p>
  
  <p>The problem does not seem to happen on Firefox.</p>
  
  <p>Unfortunately, I can't show you more code than this.</p>
  
  <p>Is this a known bug of Chrome? Are there any known workarounds?</p>