Also, attached is a screenshot of chrome://signin-internals

Deleted: Screen Shot 2018-08-29 at 10.17.22 AM.png 219 KB

	Screen Shot 2018-08-29 at 10.17.22 AM.png 219 KB View Download

Able to replicate this issue on current M68 stable#68.0.3440.106 for Mac OS X 10.13.6, however it's working fine on latest Canary# 70.0.3535.4, Dev# 70.0.3534.4 & Beta# 69.0.3497.72.

Working on bisect.

Seems like this is a known issue: https://bugs.chromium.org/p/chromium/issues/detail?id=845348

Just adding my virtual voice to the thousands of others that are having this exact same problem: Chrome signing me out every time I close the browser.

Done all the things one is supposed to do: extension management, create a new profile, create new folders, etc etc etc.

No difference.

One would hope that such a basic issue like this would be handled before releasing it to the public.

Apparently not.

Scribble... as the submitter of this bug I understand your frustration. As a fellow software engineer, I also understand the complexity of building and releasing software. It's not as simple as you would seem to think, nor is this bug due to negligence as you seem to imply.

To the engineers: thanks so much for looking into it, and please let me know if there's anything I can do to help.

There is a planned M69 stable release preferably next week and this issue won't exists on that build.

Thanks. For the record, this is also happening on the latest Canary 70.0.3538.0.

Deleted: Screen Shot 2018-08-31 at 8.08.12 AM.png 174 KB

	Screen Shot 2018-08-31 at 8.08.12 AM.png 174 KB View Download

This looks like it might be another keychain/decryption issue. There's Issue 878686, but I think that's focused on Windows.

cfroussios@ - can you take a look? Is there any additional info you need from the reporter to debug?

Yes, this is probably the same error, however note that the screenshot sent above is slightly different than the usual:

It doesn't say "failed with decrypt error", it says "failed with no refresh token".

That means that for this particular run of Chrome, the token database was loaded successfully, but it did not contain a token for the sync account.

Here is where that error is created:
https://cs.chromium.org/chromium/src/chrome/browser/signin/mutable_profile_oauth2_token_service_delegate.cc?rcl=b82224bccdc9543cc7bface3b14c21945ddc6810&l=565

My suspicion is that it is still an encryption error (if it were just a token or Google signin problem, then the cookies for unrelated webservices would not disappear). All cookies and all tokens disappearing is a very characteristic symptom of the encryption issues.

What may have happened here is that the user signed into Chrome on the previous run of Chrome, and we failed to save their token in the keychain (because of the encryption error).
At the next restart, the decrypt error did not happen, but the token was missing. The screenshot was taken at this time, which explains that error message.

cfroussios: Last time I checked our metrics, these encryption issues were quite frequent, and users (rightly) complain about this. Is there something we could do as a workaround for OS keychain issues? For example, could we stop using the OS keychain entirely?

re #14
If you are suggesting to stop using encryption altogether and leave it to the users to secure their own drives, that's a discussion between the component owners and the security team.

W.r.t to workarounds, I am not aware of any alternative ways of guaranteeing that the data is encrypted on disc (disclaimer, I know very little about macs). I am also not aware of any way to guarantee that Keychain won't start misbehaving. The solution usually is to just restart the machine when the problem occurs.

One thing that was discussed in the past was to show a warning when there are encryption errors (we can know whether it's Keychain's fault or an invalid string). The warning would then lead to a help article, which would basically tell you to restart your mac if you've done everything else right. It hasn't happened yet because nobody picked it up.

Restarting does not fix the issue.

If I understand #13 correctly, this error can carry into the next run. Please restart Chrome at least once after restarting your machine.

If the problem still persists, please run Chrome with the following arguments:
--enable-logging --vmodule=*os_crypt*=1,*keychain_password*=1
Then attach here the file chrome_debug.log from Chrome's data directory.

Thanks. I will (tentatively) confirm that the following steps do resolve the issue:

1. Restart mac
2. Open Chrome
3. Quit Chrome
4. Open Chrome again
5. Sign in to Chrome
6. Quit Chrome
7. Open Chrome. Hurrah, its still signed in.

Thank you for confirming! I will therefore close this issue.

For future reference, I would expect a simpler sequence of steps would correct the issue:
1. Problem starts occurring
2. Restart mac.
3. Open Chrome. You're still logged out of everything.
4. Sign in. This time it will stay if you restart Chrome.

If the issue reappears and the steps above (or in comment #18) don't solve it, please open a new bug and post logs as described in comment #17.