Auto-fill login data can take minutes before it works after initial launch of Chrome
Reported by
de...@derekgordon.com,
Jun 25 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: 1. Boot Ubuntu 2. Open Chrome 3. Go to any website where passwords are stored in Chrome 4. Click and no drop-down box appears for username 5. Type username, no drop-down box appears for password 6. Type password and sign in as if it was not saved. 7. Repeat at any other website and same results. 7. Minutes later, go to the same website or any other website and data will be ready to auto-complete. Twist in the puzzle, auto-complete takes about 2-3 seconds to show up when you click once it is functional. What is the expected behavior? Auto complete of saved data should instantly work on Ubuntu just like it does on our Chromebooks and on Windows. What went wrong? Auto complete data does not load right away once the browser is initially launched after a reboot. It takes a while for it to start working -and- it is slow to respond once the data does start popping up on websites. Did this work before? N/A Chrome version: 51.0.2704.103 Channel: n/a OS Version: Ubuntu 14.04 Flash Version: Shockwave Flash 22.0 r0 I believe this is similar to Issue 389139 which was closed ages ago as Won't Fix.
,
Jun 28 2016
Unable to reproduce the issue on Ubuntu 14.04 using chrome latest stable M51-51.0.2704.106 by following steps mentioned in the comment #0. Observed auto complete of saved data is shown in the drop down while typing the username field. Is this issue seen across all webpages? If it's specific to any webpage please let us know on which site you are able to repro. Could you please recheck this issue by creating a new profile under chrome;//settings without any apps or extensions in your browser. Thanks!
,
Jun 28 2016
Yes, and others report the same elsewhere. The only fix is to launch Chrome using "--password-store=basic" flag. By doing so, all passwords across all websites instantly fill. Otherwise, it's a long wait. Further, the wait is increased exponentially by the amount of passwords being stored in the Gnome keyring (standard way Chrome handles passwords on Ubuntu).
,
Jun 28 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 30 2016
Thanks for the report, and sorry for the trouble. Using Gnome Keyring is causing a lot of performance headaches for Chrome, examples including bug 489030 and bug 616085. While using the Keyring has its benefits, it also has a large maintenance burden. The balance is tipping much more towards the burden, given the low number of affected users, so we decided to migrate off using Keyring for storing passwords (we will still use it to store the encryption key for passwords). This is tracked in bug 571003. We focus on the migration instead of fixing the particular issues, because the migration is needed and the bugs will disappear once it is done. I'll still leave this report open for us to check it's fixed once we migrate away from the Keyring.
,
Dec 9 2016
Is migration done?
,
Apr 24 2017
,
Apr 25 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 26 2018
The work on migration has been started.
,
Apr 26 2018
Issue 650387 has been merged into this issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by de...@derekgordon.com
, Jun 25 2016