I had this same problem. Confirming it is fixed in 66.0.3334.0 Canary. Hope it will be in beta soon, thanks.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/69ec2285028f3261757b8e3edc6f64316c085186

commit 69ec2285028f3261757b8e3edc6f64316c085186
Author: Randy Smith <rdsmith@chromium.org>
Date: Mon Jan 29 20:35:23 2018

Revert section of
https://chromium-review.googlesource.com/c/chromium/src/+/775606 that is
causing collisions on cookie creation time.

This is a quick fix of problems
being seen in the field; a longer term fix is being tracked in
 http://crbug.com/800414 .

Bug:  800414 
Bug:  795827 
Bug:  794453 
Change-Id: I0ff206fdc517e20f270cebadc6b64704f4c18d21
Reviewed-on: https://chromium-review.googlesource.com/889958
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Randy Smith <rdsmith@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#532152}(cherry picked from commit e6515d6ae158f5b53b8ee697cdd99d714a8ab402)
Reviewed-on: https://chromium-review.googlesource.com/891642
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/branch-heads/3325@{#153}
Cr-Branched-From: bc084a8b5afa3744a74927344e304c02ae54189f-refs/heads/master@{#530369}
[modify] https://crrev.com/69ec2285028f3261757b8e3edc6f64316c085186/net/url_request/url_request_http_job.cc

+ "OS=Chrome" in case if it exists there as well.

Unable to reproduce the issue on 64.0.3282.132/10176.62.0(Eve), 64.0.3282.122/10176.61.0 (Reks)

Hello all, it's probably unrelated. All my Intel powered machines have this
issue, but my AMD machine does not.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d4965708362a62489b05e8d447b59cc101789369

commit d4965708362a62489b05e8d447b59cc101789369
Author: Randy Smith <rdsmith@chromium.org>
Date: Mon Jan 29 23:46:43 2018

Revert section of
https://chromium-review.googlesource.com/c/chromium/src/+/775606 that is
causing collisions on cookie creation time.

This is a quick fix of problems
being seen in the field; a longer term fix is being tracked in
 http://crbug.com/800414 .

Bug:  800414 
Bug:  795827 
Bug:  794453 
Change-Id: I0ff206fdc517e20f270cebadc6b64704f4c18d21
Reviewed-on: https://chromium-review.googlesource.com/889958
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Randy Smith <rdsmith@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#532152}(cherry picked from commit e6515d6ae158f5b53b8ee697cdd99d714a8ab402)
Reviewed-on: https://chromium-review.googlesource.com/891564
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/branch-heads/3282@{#610}
Cr-Branched-From: 5fdc0fab22ce7efd32532ee989b223fa12f8171e-refs/heads/master@{#520840}
[modify] https://crrev.com/d4965708362a62489b05e8d447b59cc101789369/net/url_request/url_request_http_job.cc

Impacted folks watching this bug: Fixes have been landed on the appropriate release branches, and will arrive to your desktop via auto-update over the next few days. Sorry for disrupting your workflows, and thank you for your patience!

I've got the same issue. Tried reinstalling chrome but had no luck. 
Does the above comment mean that the problem will resolve itself in a few days?

#89: yes, the fix will rollout over the next few days. Thank you all for your feedback and help with recreating and identifying the issue! If you want immediate fix, you can switch to Chrome Canary version. Fix will rollout to Dev tomorrow. 

Google Chrome Version 66.0.3334.0 (Build oficial) canary (64 bits) FIXED the issue! I tried Facebook, Amazon and Google GMAIL, PHOTOS, DRIVE and YOUTUBE, and I'm still logged after close Chrome.

Thank you for the support. 

Thank you Mano for verifying the issue on latest Chrome 65.0.3325.31. 

This started happening to me today and nothing i do works. Is there a fix for this?

As #88 says, #93, updates will role out soon. Stay tuned for an update to your browser.

If I access Google, gmail,etc. threw I.E. it keeps me logged in now which it didn't do when the bug started, but still the same problem with accessing google, gmail, etc. through Chrome. Logs me out each time. Log in on I.E works but Chrome won't still.

Restricting comments on this issue for now. Until the fixes finish rolling out, it's unlikely that we'll get useful information.

 Issue 806605  has been merged into this issue.

 Issue 807650  has been merged into this issue.

Tested the issue on Mac 10.13.3 and Windows 10 using Chrome version M64 - 64.0.3282.140 as per the issue mentioned in original comment. Observed that issue is working as intended (User still seems to be logged in even after exiting the Chrome and launching the Chrome browser later and able to use other Google applications like Youtube, Google+, Drive by following steps in original comment). Hence adding TE-Verified label. Attached the screencast for reference.

Deleted: 795827.mp4 2.0 MB

	795827.mp4 2.0 MB View Download

 Issue 806594  has been merged into this issue.

 Issue 806662  has been merged into this issue.

 Issue 794453  has been merged into this issue.

 Issue 806870  has been merged into this issue.

I have good news and bad news.

The good news: We are fairly close to shipping the CL above (d4965708362a62489b05e8d447b59cc101789369) to stable. Based on the comments above, we expect that the CL will fix the problems that most people who commented are seeing.

The bad news: The CL above does not fix the bug originally reported in this issue. rdsmith@ correctly noticed that this issue was reported against 63.0.3239.108, and the CL above reverts a part of https://crrev.com/c/775606, which landed as https://crrev.com/70f8551db62e0285060875f11beee6ae4b681e07. According to omahaproxy, "Commit 70f8551d... initially landed in 64.0.3274.0".

Implications of the bad news:
1) While we expect that most folks will remained logged in across Chrome restarts after we update Stable, the fix we're shipping does not cover some situations.
2) We'll have to re-triage all the issues that have been duped against this one.

After we ship the Stable channel update, I'll re-enable comments here.

Just a quick note that the primary tracking bug for the problems we believe most people are seeing is  issue 800414 .  A longer term fix for the root cause of that problem will be tracked under that bug.

Please note that a fix was rolled out yesterday to Beta and Stable. Please update to 64.0.3282.140 to get the latest fix. 

Applying "TE-Verified-65.0.3325.31" label per comment #92.

 Issue 808384  has been merged into this issue.

Removing comment restriction, as the update seems to have propagated.

Based on comments on other bugs and individual feedback, we assume that the update works. Please do not comment to let us know it worked for you. Please only comment if you're _still_ seeing this problem _after_ updating to 64.0.3282.140.

I'm hitting the problem with the stable 64.0.3282.140 and not with the developer version of 66.0.3342.0. What is the difference b/w these two builds specific to this issue?

Hello...i downloaded version 63.0.3239.108 and tried to see if it works(and it did work). After that i clicked to update to the latest version which is the one below. And it works with this version too. Thanks for fixing this.
Google Chrome	64.0.3282.140 (Official Build) (64-bit) (cohort: 64_140_win)

Hey all,

On the community side, we're still seeing a handful of reports of this behavior from users on 64.0.3282.140.

Primary thread: https://productforums.google.com/forum/#!topic/chrome/Bux-a2b2vUw

Is there any specific information that would assist with pinning down the issue? (ex. feedback reports, logs of some kind)

Happy to help ask for that type of information, just need to know what would be most useful.

Yes, it happened to me two hours ago on a version prior to 64.0.3282.140. I was annoyed by the 2fa, but things started off gradually. Initially it would not permit login cookies but it remembered my device so no 2fa pestering. Then I fiddled with cookies, cookie file, local storage and nothing worked. Eventually I updated, and it still wouldn't work, but a few minutes ago I restarted the browser and all works fine. Some s#!77/ day!

#117 That's weird.

case: 14739644
OS: Windows 10 64bit
customer info: https://drive.google.com/open?id=1UCWFAWX_7krWeMiusUa7nIKq-6SBzfcPyex7_REe6io

User updated to Chrome 64.0.3282.140 but the issue persists. Please advise what else I can suggest the user as a troubleshoot. Thank you very much in advance!

Maybe full uninstall Chrome and it's %appdata% folders? Then reinstall an older version(63.x.xxxx) and before. Try with that version to see if it works. If it works update to the latest version through Chrome and try again. 

re #106
Afaik there is no internal Chrome feature that logs you out of non-google things. Certainly not on every restart of Chrome.

I used to have the same problem. I filled issue 775100 for this, back when I could reproduce this often enough. Could you check if that sounds similar to your experience? It is specific to Linux, therefore unrelated to what people here are experiencing.

The issue exists also on chromium-64.0.3282.140-138.1.x86_64 on openSUSE Leap 42.3

One exceptions I notice: on Trisquel forums I am not getting logged out (https://trisquel.info/en/forum). Also some other cookies seem to remain. Example: Gmail login with 2SV doesn't ask me for 2SV after browser restart but it still asks for the account password. For Facebook though I have to enter both login and 2SV each time.

I hope that gets fix soon. Really annoying.

Users can use chrome://settings/content/cookies to define a list of sites where cookies get deleted on exit or where cookies are blocked.

In 64, we changed that blocked cookies get deleted on exit if you have any "clear on exit" rule to avoid a corner case where it was possible for sites to create cookies that survived a restart even though they shouldn't. 
I don't think this change is the issue because cookies would already have been blocked before. Users who are still affected in 64.0.3282.140 should check chrome://settings/content/cookies if there are any rules for affected sites. 
It would also be useful to create a new Chrome profile and see if the issue is occuring in this new profile.

M65 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge  into the release branch ASAP. Thank you.

 Issue 805339  has been merged into this issue.

Friendly ping to get an update on this issue as it marked as M65 stable blocker & M65 stable promotion coming very soon.

Thanks..!

 Issue 808014  has been merged into this issue.

I am also hitting this bug on 65.0.3325.73 (Official Build) beta (64-bit) (cohort: Beta). On every restart I get logged out of Google web properties (I'm still logged in on yahoo.com though).

Removing M64, and targeting M65. 

 msarda@, are you able to repro same issue listed at #128 on M64 stable version 64.0.3282.168?

After a bit of investigation, it may be related to the Desktop Identity Consistency experiment, which is only M65. We suspect now this may be a server-side bug for this experiment and we're tracking it internally with the Google Identity team - see http://b/73640832

Thank you  msarda@. Will http://b/73640832 be a stable blocker for M65? 

M65 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Merge has to happen latest by 4:00 PM PT Monday (02/26/18) in order to make it to last M65 beta release next week. Thank you.

I think that the Google Identity bug should be treated separately. The CL that was landed and merged as part of this bug fixed the problem described here (getting logged out of all accounts).

govind@: Sorry for the slow reaction, and thank you for your patience and understanding!

msarda@: If http://b/73640832 uncovers a problem in Chrome's cookies handling, please file a new bug and cc me to it, or assign it to me. Thank you!

Am also having this issue every time I close out browser. Build # Version 64.0.3282.167 (Official Build) (64-bit) - OS - Solus. Thanks

Same problem here, even after last update Version 64.0.3282.186 (Official Build) (64-bit). 

Still a problem for me (Version 64.0.3282.186 (Official Build) (64-bit)).  What Chromium/Chrome version will inclulde the fix?

Workaround which I found today: delete all cookies and other browsing data and restart Chromium. After that everything works as expected.

chromium-64.0.3282.167-141.1.x86_64

After some browsing and a few restarts - the issue is back. So obviously the workaround is useful only temporarily.

Same problem here. 

macOS High Sierra
Chrome 65.0.3325.146 64 bits.

I updated yesterday to the last version and the issues started. 

My passwords don't sync (just to this machine. They work fine in my other computers, included another High Sierra Mac)

Whenever I close and reopen Chrome, I get the "Sync isn't working. Sign-in details are out of date" message and I find myself logged out from every website.

I have tried reinstalling Chrome from scratch (even deleting the ~/Library/Application Support/... folder), going to Google sync page and forcing a resync for every device... no luck.

reycat@gmail.com: The cookies and the tokens are 2 different storages. Could you please open chrome://signin-internals take a screenshot and attach it to this bug.
Note that this pages shows personal information (e.g. email), so you may want to hash that out before attaching the screenshot.

msarda@chromium.org Here you go.

Two attached files. The first one is a screenshot of my (then) current Chrome session. Already logged in, everything seeming to work alright (except my passwords, they didn't sync).

The second one is right after closing Chrome and restarting it.

Deleted: Greenshot 2018-03-08 12.38.20.png 199 KB

	Greenshot 2018-03-08 12.38.20.png 199 KB View Download

Deleted: Greenshot 2018-03-08 12.39.23.png 90.1 KB

	Greenshot 2018-03-08 12.39.23.png 90.1 KB View Download

CC+ cfroussios

reycat@gmail.com: It looks like Chrome fails to save the token used for sync on disk (and also the cookies). This happens in general as Chrome fails to encrypt the token. We rely on the OS encryption to encrypt cookies and tokens before saving them to disk.

For example, if you are on mac, then this corresponds to a case when the keychain is locked.

If this state is unexpected (you did not lock the keychain on purpose), then I suggest you restart your machine and also restart Chrome.

msarda@chromium.org  

Awesome!

That did the trick. 

Rebooting the computer is usually one of the first things I try... but in this case it was my home server, that logs continuously certain data and I wanted to avoid a gap in the timeline.

Thanks a lot. 

This isn't happening to just the 64-bit builds. I'm running Version 65.0.3325.146 (Official Build) (32-bit) and it happens to me all the time. It doesn't happen to every website that I have the "Stay Logged In" option checked on, but a few. On those, I can close a window and reopen it, literally two seconds later, and it will ask me to log in again. It's getting a bit tiring.

#146: This bug is about getting logged out on all sites. If you're reasonably sure this is a problem with Chrome, please file a new bug at crbug.com/new

Dunno is this is worth mentioning but after update to Version 65.0.3325.162 my Chrome dropped all sessions info and logout me from every page including Google-Chrome user account itself. 

But only once. I re-log everywhere and it's fine now. Even after restart.

This is still an issue for me on openSUSE Leap 42.3

[~]: rpm -q chromium 
chromium-65.0.3325.162-146.1.x86_64

Tried clearing all browser data (cache, cookies, history, everything) and restarted - and I have to relogin to sites.

FWIW I have cookies disabled by default and only enabled for particular sites.

I have this issue and did happen when I updated opera to the latest version. both are affected now with this issue.

Just downloaded Canary ( Version 67.0.3378.0 (Official Build) canary (64-bit) ) to see if this would fix the logout issue, but still having the problem. Getting logged off of all sites when Chrome is closed.

Win 10 64 bit

So far have tried:

installing Canary
Rebooting windows
removing all extensions

Issue 823803 has been merged into this issue.

This is still happening, very annoying, and is quite old now - surely it can be fixed? Back to using FF in the meantime.... :(

To people adding comments:
This bug is marked as fixed, I think the best would be to open new bugs, including the version you are using, whether you are logged out of all websites or only Google websites, and if possible include screenshots chrome://signin-internals (note that this may contain personal information).

Also please check if your settings in  chrome://settings/content/cookies are "keep local data only until you quit your browser".

I expect we have all checked that setting. Why is this marked as fixed when clearly it isn't? Opening a new bug would lose all the history here - surely better to realise it's not fixed and alter the status here? 

Oftentimes, a problem ("I'm logged out") occurs for multiple users for unrelated root cause reasons. Because this Issue has a landed patch (#87) that resolved the issue for at least some users, it makes more sense to file a new Issue with your specific info and repro steps so that it enters the regular triage process. You can easily reference this related issue in your new bug, noting that you have reproduced the problem in a build that already included the fix landed in #87. 

I've started getting this error lately on mac chrome 65.0.3325.181. Login works until browser is restarted. Have deleted the chrome data folder in Application Support\Google\Chrome which resets it, but still has same problem. Have included screenshot of signin-internals which shows a problem with the refresh token.

Deleted: chrome_error.png 271 KB

	chrome_error.png 271 KB View Download

Nevermind with my comment, it works now. Must have been the restart issue as mentioned in the earlier posts. Maybe it would be a good idea for chrome to alert the user to reboot their computer if the system's signing library fails?

New thread
https://bugs.chromium.org/p/chromium/issues/detail?id=827522

Same issue. Chrome will NOT keep logged on sessions after closing the browser, as of 8/4/18.

I am also getting logged out of everything. Started out of nowhere.

Thanks for the reports. Please file new bugs, including specific information:
- OS
- chrome version
- ideally screenshot of signin-internals
- is the issue repeatable on your side (and if so, what are the reproduction steps)
- any other information that could be relevant
- double check that chrome://settings/content/cookies is not "keep local data only until you quit your browser"
- a frequent cause for this issue is the OS keychain being locked or unresponsive. Restarting the computer may help with this.

- Windows 10
- 68.0.3440.106 (64-bit)
- screenshot attached
- not really, this happens very often (sometimes every time I put the laptop to sleep or reboot), but I can't recreate it intentionally
- I deleted the profile and created new one - didn't solve the issue, I uninstalled and installed chrome again - didn't solve the issue (Chrome works fine with the same set of extensions on my other 3 windows devices)
- as I wrote before - this happens very often after a reboot

KR,
Leszek

Deleted: Capture.PNG 72.8 KB

	Capture.PNG 72.8 KB View Download

On that screenshot you appear to be correctly signed in, both on the web and in Chrome Sync. There are no errors reported. Was this screenshot taken when the bug happened? If not, could you take a new screenshot when the bug happens?

Hello again,

the bug happened again (I woke up the laptop, when I hovered over my username the tooltip stated that my session has been "suspended" - maybe this helps)

Attached the screenshot while Chrome was bugged.

Deleted: Capture2.PNG 38.5 KB

	Capture2.PNG 38.5 KB View Download

Thanks. What I see here is "Load Credentials Failed with Decrypt Errors".

This means that Chrome could not load your personal information from the OS keychain. This is a known bug.

cfroussios@ may know more about how to mitigate the issue (try to unlock the keychain from the OS UI, reboot the computer, ...). I think at this point we believe that it is a bug of the OS. There is certainly more we could do (at minimum display an error dialog), but I don't know what are our plans here.

Thanks for getting back to me! I guess I'll have to wait for the bug, but
my other problem with being signed out of accounts every time I closed
Chrome was solved with your other advice. Thanks so much for your help - it
took away a lot of my frustration with being online.

Robyn

Regarding the case in #163 and #165, Keychain is not the problem because this is Windows. There is no Keychain on Windows. There are also no known problems with encryption in general. I'm guessing this is something the sync team should look into.

I should have been more specific
* There are no known problems with encryption on Windows in general.

Encryption continues to be a reasonable suspect on Mac and Linux.

Thanks! My short-term problems have been resolved and the long-term are an
infrequent problem that I won't worry about at this time.

Best,
Robyn

Cfroussios: It may be windows, but they still have encryption errors, as shown on the signin-internals page. What could be the cause then ?

Hello again,

I switched over to Canary hoping this is resolved but unfortunately (see screenshot) - I'm logged out after first reboot.

I don't know if someone mentioned it before but it seems that all my cookies are gone - I'm not only logged out from google account in Chrome itself. Everything else is also logged out, I also get cookie infos from sites I already visited like it is my first visit.

Deleted: Capture3.PNG 59.8 KB

	Capture3.PNG 59.8 KB View Download

The cause is definitely the decrypt error. Apparently this is a known problem for Mac and linux, but not for Windows. I'm going to move the discussion to a separate bug (bug 878686), because it seems to be a separate problem.

Recently (for about 3 weeks or so) every time I quit Chrome my Google account signs out, as well as all other accounts I use frequently, such as Facebook, Steam. I have to re authenticate with Google and all of these every time I start up Chrome.
I have ensured the Chrome setting "Keep local data only until you quit your browser" is disabled. I have tried completely clearing cookies. I have tried completely deleting my "Library/Application Support/Google/Chrome" directory, and re-created my profiles.This did not work.
Also, attached is a screenshot of chrome://signin-internals

Deleted: 01.jpg 118 KB

	01.jpg 118 KB View Download

Also My I platform is win10 1803
          version of Chrome is 68-Stable

This screenshot of signin-internals looks fine: it shows that your cookies and tokens were loaded with success, are valid, and you have a sync account configured.

Was this screenshot taken at a time where the problem was happening?

also: Library/Application Support/ is a Mac OS thing, you can't have this directory if you are using windows 10.

This is the photo when the problem occurred

also,I  try completely deleting my "C:\Users\****\AppData\Local\Google\Chrome" directory

Deleted: 02.jpg 92.2 KB

	02.jpg 92.2 KB View Download

Really- everything's fine now as far as I can see. Thanks, though.

My God!! HOw in the bloody hell do any of you expect a person like me to resolve this issue of chrome constantly signing me out, when I cannot understand how to resolve this issue????  

I'm going to go ahead and close the issue - two issues were fixed (This one and ( bug 800414 ), but clearly quite a few people are still having problems.  Unfortunately, sorting through 180 posts, some about two old issues that was fixed, some about a Windows issue that was forked to (bug 878686), and possibly still others about some other issue makes making any headway here difficult.

If you're on Windows and see a decryption error on chrome://signin-internals (Like in comment 165), please refer to (bug 878686).  If you're seeing another error, please file a new bug.