Chrome hangs on "sending request" appears to be socket related

Question

When I load the url for a rather large application I'm working on, I'd say every 3-4th reload the application hangs and stops loading. Chrome reports "sending request" in the lower left. I can't seem to identify any file its stopping up on, but instead found this thread:

https://code.google.com/p/chromium/issues/detail?id=55046

which indicates it might be a socket issue. Flushing sockets from this page (chrome://net-internals/#sockets) instantly frees up the page and everything proceeds to load normally. Here's an image from that chrome internals page

I realize that this may indeed be a chrome bug, but in the meantime, I need a workaround, since users are hitting this bug in chrome, and can't load the application. Ideas?

Answer 1

I know of 2 workarounds, none are exactly convenient though:

1. Disable SPDY: "...\chrome.exe" --use-spdy=off (unfortunately cannot be done via flags)
2. Disable Sync ("Settings - Disconnect your Google Account")

Another option is to reduce number of connections within your app (serve all static content from 1 domain + 1 websocket connection for all client-server communication), and remove widgets (twitter, disqus, etc which keep persistent connections) where possible, which may or may not help considering the socket pool is shared between all Chrome tabs :(

Personally for me this bug occurs to random websites since Chrome 21, and is somewhat countered by crashes which reset the pool :)