Chrome 暂停请求 15 秒

Question

我们有一个 Angular 2 应用程序，它会随机地将请求延迟 15 秒。问题似乎是 chrome 耗尽了 TCP/IP 连接。问题仅出现在 Chrome 中。请求在 Chrome 开发选项卡中获取连接 ID：\n显示停止且没有连接 ID

\n\n

15 秒后，响应加载为空。

\n\n

在 chrome://net-internals/#events 中，请求如下所示：

\n\n

看看 15 秒的间隙，chrome 告诉我什么？

\n\n

t=543333 [st=   50]        HTTP_STREAM_PARSER_READ_HEADERS  [dt=15062]\nt=558395 [st=15112]        HTTP_TRANSACTION_READ_RESPONSE_HEADERS\n

\n\n

全部：

\n\n

t=543283 [st=    0] +REQUEST_ALIVE  [dt=15113]\n                 --> priority = "MEDIUM"\n                 --> url = "https://www.struqtur.se/hyperion/GraphQl?hyperionRevertParapaar=6.4186284125575295"\nt=543283 [st=    0]   +URL_REQUEST_DELEGATE  [dt=1]\nt=543283 [st=    0]      DELEGATE_INFO  [dt=1]\n                     --> delegate_blocked_by = "till\xc3\xa4gget Adblock Plus"\nt=543284 [st=    1]   -URL_REQUEST_DELEGATE\nt=543284 [st=    1]   +URL_REQUEST_START_JOB  [dt=15111]\n                   --> load_flags = 258 (BYPASS_CACHE | VERIFY_EV_CERT)\n                   --> method = "POST"\n                   --> upload_id = "0"\n                   --> url = "https://www.struqtur.se/hyperion/GraphQl?hyperionRevertParapaar=6.4186284125575295"\nt=543284 [st=    1]      URL_REQUEST_DELEGATE  [dt=0]\nt=543284 [st=    1]      HTTP_CACHE_GET_BACKEND  [dt=0]\nt=543284 [st=    1]     +HTTP_STREAM_REQUEST  [dt=49]\nt=543284 [st=    1]        HTTP_STREAM_JOB_CONTROLLER_BOUND\n                       --> source_dependency = 45248 (HTTP_STREAM_JOB_CONTROLLER)\nt=543333 [st=   50]        HTTP_STREAM_REQUEST_BOUND_TO_JOB\n                       --> source_dependency = 45249 (HTTP_STREAM_JOB)\nt=543333 [st=   50]     -HTTP_STREAM_REQUEST\nt=543333 [st=   50]     +UPLOAD_DATA_STREAM_INIT  [dt=0]\nt=543333 [st=   50]        UPLOAD_DATA_STREAM_INIT  [dt=0]\n                       --> is_chunked = false\n                       --> net_error = 0 (?)\n                       --> total_size = 151\nt=543333 [st=   50]     -UPLOAD_DATA_STREAM_INIT\n                     --> is_chunked = false\n                     --> net_error = 0 (?)\n                     --> total_size = 151\nt=543333 [st=   50]     +HTTP_TRANSACTION_SEND_REQUEST  [dt=0]\nt=543333 [st=   50]        HTTP_TRANSACTION_SEND_REQUEST_HEADERS\n                       --> POST /hyperion/GraphQl?hyperionRevertParapaar=6.4186284125575295 HTTP/1.1\n                           Host: www.struqtur.se\n                           Connection: keep-alive\n                           Content-Length: 151\n                           Pragma: no-cache\n                           Cache-Control: no-cache\n                           Accept: application/json, text/plain, */*\n                           Origin: https://www.struqtur.se\n                           User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36\n                           Content-Type: application/json\n                           Referer: https://www.struqtur.se/v2/day/handle\n                           Accept-Encoding: gzip, deflate, br\n                           Accept-Language: sv-SE,sv;q=0.9,en-US;q=0.8,en;q=0.7\n                           Cookie: [408 bytes were stripped]\nt=543333 [st=   50]        HTTP_TRANSACTION_SEND_REQUEST_BODY\n                       --> did_merge = false\n                       --> is_chunked = false\n                       --> length = 151\nt=543333 [st=   50]       +UPLOAD_DATA_STREAM_READ  [dt=0]\n                       --> current_position = 0\nt=543333 [st=   50]          UPLOAD_DATA_STREAM_READ  [dt=0]\n                         --> current_position = 0\nt=543333 [st=   50]       -UPLOAD_DATA_STREAM_READ\nt=543333 [st=   50]        UPLOAD_DATA_STREAM_READ  [dt=0]\n                       --> current_position = 151\nt=543333 [st=   50]     -HTTP_TRANSACTION_SEND_REQUEST\nt=543333 [st=   50]     +HTTP_TRANSACTION_READ_HEADERS  [dt=15062]\nt=543333 [st=   50]        HTTP_STREAM_PARSER_READ_HEADERS  [dt=15062]\nt=558395 [st=15112]        HTTP_TRANSACTION_READ_RESPONSE_HEADERS\n                       --> HTTP/1.1 200 OK\n                           Date: Mon, 11 Dec 2017 09:01:54 GMT\n                           Server: Apache\n                           Expires: Thu, 19 Nov 1981 08:52:00 GMT\n                           Cache-Control: no-cache, no-transform\n                           Pragma: no-cache\n                           Content-Length: 53\n                           Connection: close\n                           Content-Type: application/json\nt=558395 [st=15112]     -HTTP_TRANSACTION_READ_HEADERS\nt=558395 [st=15112]      URL_REQUEST_DELEGATE  [dt=0]\nt=558395 [st=15112]   -URL_REQUEST_START_JOB\nt=558395 [st=15112]    URL_REQUEST_DELEGATE  [dt=0]\nt=558395 [st=15112]    HTTP_TRANSACTION_READ_BODY  [dt=0]\nt=558395 [st=15112]    URL_REQUEST_JOB_FILTERED_BYTES_READ\n                   --> byte_count = 53\nt=558395 [st=15112]    HTTP_TRANSACTION_READ_BODY  [dt=1]\nt=558396 [st=15113] -REQUEST_ALIVE\n

\n\n

Chrome 开发选项卡中已完成请求

\n\n

我读过很多帖子并试图解决问题但没有运气

\n\n

对同一资源发出多个请求时 Chrome 会停止运行？

\n\n

https://bugs.chromium.org/p/chromium/issues/detail?id=46104

\n\n

https://bugs.chromium.org/p/chromium/issues/detail?id=447463

\n\n

我发现的线程/问题是相似的，但解决方案不起作用 s\xc3\xa5 我希望有人有此类问题的经验并有任何想法

\n

Answer 1

我在 Chrome 上遇到了同样的问题，但我的应用程序不使用 Angular。但是，net-internals/#events发生停滞请求时​​，其条目是相同的，并且通常受影响的请求同样会停滞长达 15 秒，但通常更接近 5-10 秒。

就我而言，当应用程序访问内部 API 时，就会发生这种情况，并且服务器端日志对于停滞的请求来说是完全正常的（即 API 调用不会比平时花费更长的时间），所以我知道这是 Chrome 中的问题。客户端应用程序部署在 Chromebox 上，这可能很重要，因为我无法在我的工作站上重现该问题。

@torpare-nilsson 你有找到更多关于这个的信息吗？我看到你在 Angular 的 GitHub 上打开了一个问题，但被退回到 SO，这可能是有道理的，因为这看起来是一个 Chrome 问题。