Chrome/Chromium hang at startup
Reported by
sfch...@gmail.com,
Mar 7 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36 Steps to reproduce the problem: After I wake up my windows 10 pc from an overnight sleep, I wasn't able to start Chrome or Chromium at all. What is the expected behavior? What went wrong? I attached to the hanging process with a VS debugger and found the call to ::GetAppliedGPOList never returns. Further investigation found that the group policy client service is not functioning on my system. Therefore, this is not exactly a chrome problem. However, the group policy client service problem does happen a lot on my system for some reason. Having chrome hang at startup without any error message would really confuse the users. I've personally got reports from many other chrome users who complain they are not able to open their Chrome. They click on the icon and nothing happens. Most probably their problem could be caused by the same reason. There should be a more graceful to address this problem. For example, we should check if the group policy client service is actually running at startup. If it is not running, we can let chrome continue to run without applying the group policy. Did this work before? N/A Chrome version: 48.0.2564.97 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 20.0 r0
,
Mar 7 2016
,
Mar 7 2016
,
Mar 8 2016
Can you provide any extra information about why the call never returns? Some things that would help would be call stack and the list of loaded DLLs, or even a minidump taken at point of hang if you're willing to share one.
,
Apr 4 2016
,
Jan 17 2017
I also have a GPO enterprise environment and users returning since after Christmas break are complaining that they are having this issue. I've gone in to the taskmgr and I see about 3 chrome.exe processes running. If I kill them all, chrome will then start.
,
Jan 19 2017
Could you use a tool such as Process Explorer, Process Hacker, or windbg to capture a memory dump of the seemingly-hung browser process (the one of those 3 chrome.exe processes that is the parent of the other two)? This would help us determine whether or not this is the same issue or something new. Thanks.
,
Apr 11 2017
One of our users encountered same problem, we were able to remotely connect to and debug browser. After browser is launched, main browser thread is stuck inside call to ::GetAppliedGPOList winapi function. This function does not return result for 5-7 minutes. After 5-7 minutes browser continues to work as intended. If we go to chrome://policy page and press "Reload policies" button, this function (::GetAppliedGPOList) is called again and again it does not return execution for several minutes. Only this time browser interface is not blocked, because this time function is executed on file thread. Problem is reproduced on Windows 8.1 corporative edition. Windows is not connected to domain, only to workgroup. Computer has "Total security 360" antivirus software installed. I think we need to to add some diagnostics first - for example histogram for ::GetAppliedGPOList function execution time to evaluate scale of problem.
,
Apr 11 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by phistuck@chromium.org
, Mar 7 2016Components: Enterprise
Labels: Stability-Hang