[+rdsmith]:  I asked Rik to file this bug.  Sounds like this problem started with Chrome 64.0.3282.119, and was not fixde with the *.119 release.

Any chance the cookie database could end up corrupted as a result of the duplicate-time bug, and end up in a wedged state?  I had him delete cookies manually using the "CookieTree" API (security badge->cookies), but that didn't seem to have helped.  I'm a bit concerned that other users may also be in some sort of wedged cookie state, though not completely sure this is a cookie issue.

[+pwnall]

I wouldn't expect that there's a way for the cookie DB to get wedged.  SQLite's behavior in this case is well specified--the uniqueness constraint is violated, so the add fails.  Victor, do you have a different perspective? 

Note that there is a known other problem that results in loss of credentials that's being tracked by  issue 795827 , and we have no clue as to whether or not cookies are involved in that one.  Victor thought he had a repro in his profile that suggested it wasn't cookies and was going to follow up with the appropriate people about it; Victor, any update on that?

To my surprise, the problem didn't repro for me after the .140 update.

@msarda: Are there debugging steps for generic "losing my credentials" problmes that you'd recommend?  I unfortunately don't have a lot of useful tools to probe at what's happening with the cookies.

Unable to reproduce this issue on reported version 64.0.3282.140 with steps given in comment#0.

1. Installed 64.0.3282.71  signed in chrome with valid credentials,  upgraded to 64.0.3282.119 and didn't observe any sign out from google accounts.
2. Upgraded from 64.0.3282.119 to 64.0.3282.140 and even now didn't observe any sign out.

As per online summary this issue is seen randomly. Could someone from Internals>Network>Cookies team please have a look at this issue.

Thanks!

I think we need to isolate and see if this is a Google-only issue or not.

Is this a Google-only issue or is the user being signed out of other sites (e.g. facebook, yahoo etc)?

If this is a bug that you only see for Gmail and other Google web properties, then we should be able to investigate this on the server as well.

I am adding also some engineers from Google auth that may be help us understand what is going wrong with the cookies.

rik.windspear@gmail.com@: We would need help from you to investigate this server-side to better isolate the problem. To do that, a Google auth engineer would need to look over the internal logs. To do that, we would need explicit consent from you that you allow the engineers to check the sign-in and sign-out logs for your account.

If you accept to consent to this, then I would ask you to do the following:
* Start Chrome in the broken state
* Sign in to gmail with your account
* Go to https://accounts.google.com/ReportBug and copy the bug number showed on that page to this bug report.
* Quit Chrome and restart
* Tell us if you hit the same bug.

Hi,

Thanks for looking into this. I give consent to allow the engineers to check the logs. When the bug happens again, I will be sure to do those steps and report back.

Currently everything is working fine.  The temporary solution seems to be explicitly signing out of Gmail and then signing back in. If you need any other information please let me know, I would be glad to assist with this issue.

Sincerely,
Rik

Thank you for providing more feedback. Adding requester "msarda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Adding back needs feedback - I don't think we can proceed without the data requested in comment #9 (Bug number from ReportBug).

Closing because of inactivity. Please reopen if you can provide the requested information.