Issue metadata
Sign in to add a comment
|
On first launch Chrome takes about 1 to 2 minutes before it will function
Reported by
lazzl0...@gmail.com,
Mar 13 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Linux; Android 7.0; SM-T820 Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.109 Safari/537.36 Steps to reproduce the problem: 1. Open Google Chrome 2. Try to type in browser What is the expected behavior? Can either type in browser or navigate to a website What went wrong? There is no error and task manager does not show any CPU usage issues. The browser either does not accept input or, if it does, will not navigate to a site for 1 to 2 minutes Did this work before? Yes Prior to 64.0.3282.186 Chrome version: 65.0.3325.109 Channel: stable OS Version: 7 Flash Version: Once the initial delay has passed, the given session of Google Chrome works normally.
,
Mar 14 2018
Thanks for filing the issue! @lazzl0ngz: Could you please check the same issue on the latest stable 65.0.3325.162, as we are unable to see any delay after entering some text in search bar with the chrome version 65.0.3325.106 and on the latest stable 65.0.3325.162. Please find the below link to download the latest chrome versions. https://www.chromium.org/getting-involved/dev-channel Please let us know if the issue still persists on the latest stable. Any further inputs from your end may help us to triage the issue in a better way.
,
Mar 14 2018
This issue has impacted at least 5 people in our organization (out of several hundred). We first started seeing it in mid February, which would have been 64.0.3282.186. Updating to 65.0.3325.109 did not resolve it; I spoke with one user this morning that is still having this issue and is on 65.0.3325.162. We have confirmed disabling extensions and uninstalling/reinstalling does not resolve this. We have also confirmed it is not network related as it happens when connected to different networks, and the same delay does not happen in Internet Explorer.
,
Mar 14 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 15 2018
Unable to reproduce the issue on chrome version 65.0.3325.106 and on the latest stable 65.0.3325.162 using Windows 7 with the below mentioned steps. 1. Launched chrome 2. Typed some random text and hit enter We are able to type the content properly with out any issue and after hitting enter chrome navigated to respective content/site without any delay. Attaching the screen cast of the same. As the issue is not reproducible from our end, removing Needs-Bisect label and requesting someone from "UI>Browser" team to have a look into it. Thanks!
,
Mar 16 2018
I have not been able to reproduce this issue either. I have reached out to the people that are having this issue to collect data from their machines; aside from the content of %localappdata%\Google\Chrome\User Data, what else would be useful?
,
Mar 16 2018
I have created a Box folder share where I will put the content from the User Data folders: https://tklaw.box.com/s/r4hm0ocy9b7gufyyulkm5vxt9bz01wc2
,
Mar 19 2018
As this issue is not consistently reproducible from TE end, hence adding label "TE-NeedsTriageHelp" and requesting someone from "UI>Browser" team to have a look into it and help in triaging the issue further. Thanks!
,
Apr 2 2018
This continues to be an issue for a small group of people in our firm. I do not think this is caused by an extension as at least one person does not have any extensions, but wonder what else we could look at that would be helpful in resolving this.
,
Apr 2 2018
I have attached a file listing of the User Data folder for two people having this issue. Please let me know what information would be useful and how I can remove any personal data before providing this
,
Apr 3 2018
I have noticed those individuals still having this issue can begin typing in Chrome immediately but it still takes a couple minutes to open a website.
,
Apr 10 2018
This issue appears to be user profile specific; deleting/renaming %localusersdata%\Google\Chrome\User Data has resolved the issue for at least one user. We tried resetting Chrome's settings but this did not resolve it. It has only been a day since this was done, so we do not know if this issue will come back. We also do not know what caused this to begin with.
,
Nov 22
*** UI Mass Triage *** We were unable to reproduce this bug. If this bug still reproduces for you, please reopen or file a new issue. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Mar 14 2018