How to debug frequent request stalling issue?

[Mohamed Lrhazi]

Hello,

Chrome and Chromium, frequently stall while loading pages from several of our web sites proxied by an F5 loadbalancer. How do I go about finding the root cause?

By stalling I mean that one or a couple of requests, in the network tab of the devtools, shows they took a long time, all of which was in the stalled phase.

I can reproduce this issue by simply loading the homepgae of one such web sites, and then refreshing the page a few times, with caching disabled... fairly quickly I would get one, two or even three requests to take full minute or two, instead of sub second times. 

I could not reproduce this behavior using Firefox, only with Chrome and Chromium, on MacOS and Windows.

Thanks a lot,

Mohamed.

[PhistucK]

Are you browsing using a proxy (for example, browsing from within a corporate network)?

If so, is Firefox also configured to use that proxy?

I am asking because Chrome uses the system proxy settings by default while Firefox does not and if the proxy is actually stalling the request, that would be a reason why in Chrome it is stalled while in Firefox it is not.

If both of them use the same proxy (or no proxy is configured in the system and Firefox as well), then this is probably not the issue and you should file an issue at crbug.com (if you have not found an existing one) with a network log attached.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[Mohamed Lrhazi]

No, no proxy in use. I opened a bug here: https://bugs.chromium.org/p/chromium/issues/detail?id=1009151#c5

Thanks a lot.

If anyone is curious, I would love to know if you can reproduce this  issue:

1- Load this website, with DevTools open and caching disabled.

https://oem-debug.cua.edu/em/

2- Wait some 10 seconds or so.

3- Re-load the page

- You should get some stalled requests, if not please try again from step 2.

[Przemysław Lib]

Was there any progress on this topic?

Where you able to investigate root cause at a greater resolution the "Stalled"?

To unsubscribe from this group and stop receiving emails from it, send an email to chromium...@chromium.org.

[Mohamed Lrhazi]

Yes. It turns out Chrome does send the full request out to the server, but receives no reply. 45 seconds later tcp keepalive causes the connection to close down, then Chrome retries using a different TCP connection, and either hangs again on server failing to reply, or succeeds. 

It appears all the time spent waiting on these bad connections goes under "Stalled" time, which is probably a bug. I am planning on file a bug agaisnt DevTools for this. Thanks.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.