Chrome XmlHttpRequest Hanging

Question

When I create an XmlHttpRequest (via jQuery $ .ajax) for a specific URL, my Chrome constantly hangs every time with the status for the request "Waiting".

After that, Chrome should be closed, i.e. forced from the task manager, and it detects common signs of chaos, such as the Cookies and Scripts tabs, empty when they were filled with normal looking data immediately before it.

This is strange because (a) my colleagues, who seem to be all the same, do not have such problems; (b) I have been using Chrome to run this code (our JavaScript application in our company) for many months, and this has just begun to happen for no apparent reason.

I checked the Apache logs, they seem to process the request as usual until completion, but Chrome never sees the answer, apparently.

A few other explanations: to failure, the same Chrome and Apache return the JS truck and image files, as a rule, for example, everything looks fine until they become. The request is not particularly large (several hundred bytes in and out) or complicated in any obvious way.

If anyone can give me some hints about where to look, I would be grateful!

Answer 1

I experience similar behavior with slightly different symptoms. My ajax requests work fine, every second request up to 6 requests, then they all start to fail (same url as when working, same payload, etc.), but in my case they don’t even get on server, just stuck in "Waiting" in the inspector.

I have no answer for you, but in order to help debug, have they tried clean internal elements?

Point your browser at:

chrome://net-internals/#sockets 

and / or

 chrome://net-internals/#events 

I see that my requests in #sockets become active, but never return, and in #events I see that the request stops after the HOST_RESOLVER_IMPL_REQUEST stage.

I think this may be a resource problem caused by the incorrect termination of the request, but this is just pure speculation.