legendmove@ Thanks for the issue.

tested this issue on Ubuntu 14.04 and Windows 10 on the latest canary 66.0.3328.0 and stable 63.0.3239.132 by following the below steps.

1. Launched Chrome and navigated to https://reviewmeta.com/.
2. Clicked on an Amazon item and clicked on Run report and in a new tab navigated to https://reviewmeta.com/.
Attached is the screen cast for reference.

Can you please provide a screen cast of the steps followed for better understanding of the issue.

Thanks..

Deleted: 804146.webm 7.0 MB

	804146.webm 7.0 MB View Download

ignore the first item, no update available

1. I clicked update on the second item, while the page was loading, it blocks connection on all other tabs to the same site (reviewmeta.com), either waiting for cache or waiting for site. Note that in dev console network pane, other tabs were not even attempting an HTTP request.
2. once the page finishes loading, all other tabs to the same site were no longer blocked

Deleted: chromium_reviewmeta_connection_blocking.gif 6.5 MB

	chromium_reviewmeta_connection_blocking.gif 6.5 MB View Download

Thank you for providing more feedback. Adding requester "susanjunia.boorgula@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for the report.

Can you reproduce the problem on other browsers?

I agree with your assessment that it is probably stalled waiting for sockets (origins only get 6, so can block waiting for sockets).

Can you capture a NetLog dump?

For instructions see: https://dev.chromium.org/for-testers/providing-network-details

I can recreate this with Firefox ESR 52.5.3. Similar to Chromium, private window is not affected.

NetLog attached

Deleted: chrome-net-export-log_reviewmeta_blocking.json 5.6 MB

chrome-net-export-log_reviewmeta_blocking.json 5.6 MB View Download

Thank you for providing more feedback. Adding requester "eroman@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks.

Sounds like an issue with the website then, with the best resolution being to contact them about this use-case.

For the slowest requests, getting a response from reviewmeta.com takes over 40 seconds (reading response headers). In 2 other requests it takes 13 seconds to get a response (after having already waited 20 seconds for the cache lock - ERR_CACHE_LOCK_TIMEOUT).

+Shivani FYI cache lock.

Looks like it's server side cookie based connection limit. I cleared cookies after starting a review update, other tabs loaded instantly while the update is still in progress. I wonder why it didn't wait for cache lock this time.