Chrome freezes when Domain Controller is slow to respond
Reported by
ya...@silverfort.io,
Apr 13 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Try to access a webpage with Kerberos authentication (the web page should be in the corporate domain). 2. Delay Domain Controller's response 3. Chromium freezes (all tabs!) until response is received by Domain Controller. What is the expected behavior? Only the tab with the webpage is supposed to freeze. What went wrong? The main IO thread is blocked by a call to the InitializeSecurityContext API call. This API call sends a TGS_REQ to the Domain controller, which is supposed to return a TGS_REP. If, however, the Domain Controller fails to return the response, the API call never returns. This API call is called from the IO thread, so as a result all of the tabs become unresponsive. Did this work before? No Chrome version: 57.0.2987.133 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 25.0 r0 A related bug is this one: https://bugs.chromium.org/p/chromium/issues/detail?id=42222# From the discussion: "There are some additional components which may need to be async, but I'll consider this fixed until histograms indicate we need to do additional work." These additional components should become async to fix this problem.
,
Apr 13 2017
https://chromium-review.googlesource.com/c/477011/
,
Mar 15 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by mmenke@chromium.org
, Apr 13 2017