Overview
A defect exists in Chrome where there is a long delay for certain requests due to stale connections/sockets. When using the Chrome Monitor in a Web, Transaction, Playwright, or Puppeteer test, certain requests may intermittently timeout during connect or have long (30+ seconds) blocked time.
Catchpoint Test Result
Since the Catchpoint Chrome monitor's logic is to end the test at a certain point, if the request is still in the queue, it will be ended and shown as a test timeout with some requests having long Connect time. This is different from when a test takes too long in general and all the current requests on the wire get terminated, which results in a block of requests at the end of the test having long Connect times.
This behavior will usually manifest as one or multiple requests in the middle of the waterfall hanging on connect. If extended timeout is used, requests may appear with extended block time (30s to a minute, or more) after which the request is completed quickly.
External links
For more information on the Chrome defect, please visit:
https://bugs.chromium.org/p/chromium/issues/detail?id=447463