Limiting sockets per domain makes browsing some sites very frustrating
Reported by
netmosf...@gmail.com,
Dec 27
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Example URL: Steps to reproduce the problem: Please read carefully. I'm spending my unpaid time to write this bug report, please do spend your time to actually read it, if that's your job. I'm constantly getting "Waiting for available socket..." in the statusbar when I open multiple tabs from the same site. This happens with new profiles also, without extensions. Unfortunately many sites just fail at loading rather than just being slow at loading because of this issue. Happens with even just 3 tabs. I have a high speed connection and I don't have such problems with Firefox, presumably because it allows more connections per domain. I saw it happening on time.com or theverge.com What is the expected behavior? What went wrong? Loading is very slow, eventually loading partly fails, page is unresponsive, like buttons don't work and stuff like that. Did this work before? N/A Chrome version: 71.0.3578.98 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Dec 27
Thanks for filing the issue! Tried checking the issue on reported chrome version 71.0.3578.98 using Windows 10 with the below mentioned steps. 1. Launched Chrome 2. Navigated to http://time.com/ 3. Opened few other tabs from the above site. We didn't observe "Waiting for available socket...." in the process. Note: Tentatively adding component "Blink>Network>WebSockets", please change if this isn't apt. @Reporter: Could you please let us know if this is specific to any/certain Network(s). Any further inputs from your end may be helpful.
,
Jan 2
I believe that Firefox still shares many of the same connection limits as Chrome, as ours originally came from mirroring Firefox's (and were then increased a little) If you can attach a Network Log, as per https://dev.chromium.org/for-testers/providing-network-details , then we can work to better understand what's causing these issues. There are some global limits to the number of pending sockets, so it's possible you're hitting those. A NetLog will help confirm.
,
Jan 2
Since it doesn't happen all the time, how do I make sure that I did actually capture the problem? What should I look for in the json produced by the network log tool? thank you
,
Jan 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 2
You can create a chrome://net-export/ dump after things start to hang. Start capturing, then open some new tabs, and then stop the capture. The NetExport log contains a snapshot of the currently open sockets, so will at least show how the sockets have been allocated.
,
Jan 11
Please provide the requested NetLog or we will have to close this bug :(
,
Today
(12 hours ago)
Closing due to inactivity after requesting logging. Please open a new bug and provide the logging if you are still experiencing the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by viswa.karala@chromium.org
, Dec 27