While I would love to be able to report this rather unfortunate bug while telling you that the last bug we reported was remedied, that is not the case.
The issue: when going to Settings > Show Advanced Settings > Manage Passwords the pop-up window that displays all your saved passwords simply freezes and displays nothing. Eventually the settings tab/window crashes completely and has to be closed.
We are starting to see this appear in the help Forums and we have reported a bug as well. There is a workaround, but it isn’t great and this bug needs serious attention.
To be fair, I’m still in the Beta channel even after the Stable update to M53 was supposed to fix the Chrome crashing bug we reported on last week. So far, it has not, so with the account I’m having this current issue with I cannot get Stable up and running long enough to test whether or not this is happening there or not.
I can confirm that on other accounts, the issue is not persisting, so this is similar to the earlier bug in that it seems to follow your Google Sync account.
I tried powerwashing, exiting and entering Dev mode. Nothing has worked on that end. I even cleared my Google Sync completely with no luck.
The only workaround I’ve found thus far is to turn off the option to “Encrypt all synced data with your own syn passphrase.” This can be found in Settings > Advanced Sync Settings > Encryption Options.
Once this is set to “Encrypt synced passwords with your Google Credentials,” you can then go to passwords.google.com in order to manage and see your passwords. If you leave the unique encryption on, the URL just mentioned will not allow you to view your passwords.
For me, password management has been one of my favorite things about being a Chrome OS user. The ability to have auto-fill and quickly go into settings to see my passwords (sharing with co-workers and clients on projects) has been a valuable feature. This morning, not having access to those passwords cost me quite a bit of time hunting them down.
That’s why we wanted to offer up this bug report and work-around. Hopefully both of the discussed bugs get fixed soon.