Unable to reproduce the issue on reported chrome version 63.0.3239.84 and latest canary 65.0.3293.0 with steps mentioned below:

Steps followed to reproduce the issue:
1) Launched chrome reported version
2) Logged into gmail
3) Exicted from browser
4) Launched browser again
5) click on gmail link on top right corner
6) Able to login into gmail again

@Reporter: Please find the attached screencast for your reference, please try to test the issue by creating the new person with no extensions and apps in it and let un know if the issue still persists

Thanks!

Deleted: 794453_Stable.mp4 3.6 MB

	794453_Stable.mp4 3.6 MB View Download

Deleted: 794453_Canary.mp4 3.9 MB

	794453_Canary.mp4 3.9 MB View Download

Google Chrome	65.0.3294.2 (Offizieller Build) canary (64-Bit) (cohort: Clang-64)
Überarbeitung	a40aaa798fdd2ff4111f7924fbb9899e545a0053-refs/branch-heads/3294@{#2}
Betriebssystem	Windows
JavaScript	V8 6.5.56
Flash	28.0.0.133 C:\Users\Winkler\AppData\Local\Google\Chrome SxS\User Data\PepperFlash\28.0.0.133\pepflashplayer.dll
User-Agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3294.2 Safari/537.36
Befehlszeile	"C:\Users\Winkler\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --flag-switches-begin --flag-switches-end
Ausführbarer Pfad	C:\Users\Winkler\AppData\Local\Google\Chrome SxS\Application\chrome.exe
Profilpfad	C:\Users\Winkler\AppData\Local\Google\Chrome SxS\User Data\Default
Varianten	fe69e053-83ce3e87
16e0dd70-3f4a17df
da89714-4ad60575
64da5c1e-c3f95060
9041608a-f23d1dea
1e528f0f-ca7d8d80
b130ecb8-2e32ee7e
6025934e-3f4a17df
7c1bc906-86bf56d9
d52c4ff7-d52c4ff7
3eb101d6-f23d1dea
47e5d3db-3d47f4f4
a5cb8590-f23d1dea
34d450b1-1410f10
459a590c-1426d30a
19c1fdaf-3d47f4f4
3042ad4b-cf4f6ead
9e201a2b-38d7ffb9
591576c8-ca7d8d80
57f575bb-f23d1dea
e4e9ce8f-3f4a17df
b72f69e9-f23d1dea
f347910c-3f4a17df
4b61504a-d92031a1
77bbdddc-c65eb556
5485fc4d-ca7d8d80
8fa604e0-f23d1dea
8e3b2dc5-93702590
9e5c75f1-20ba8a0b
9f6e28b-99878ea
3de1fbf2-f23d1dea
f79cb77b-3f4a17df
47edb3-566ebc9b
274c53f-3f4a17df
4ea303a6-9f93d4fc
bcc34a89-ca7d8d80
12be2281-3f4a17df
d92562a9-ca7d8d80
90bcbadc-7737cf5f
447469ba-13d9f35f
7aa46da5-c946b150
2b33233e-d8253d6f
6973a1cf-f23d1dea
72606c4f-3f4a17df
1aecb842-3f4a17df
ad6d27cc-7075cd8
757a5d98-3677ae14
f3ea30a0-27a0c3c6
23496387-4ea78229
b2f0086-d3486be4
3038aa2e-f23d1dea
2d871858-3f4a17df
344833e9-1525b35b
4bc337ce-612a79a3
1354da85-ca7d8d80
3ac60855-486e2a9c
f296190c-7564fb06
4442aae2-a5822863
ed1d377-e1cc0f14
75f0f0a0-d7f6b13c
e2b18481-e1cc0f14
e7e71889-e1cc0f14
b1ceb06f-3f4a17df
34baa302-cf4f6ead
f5fff3a2-3f4a17df
9cade933-6a0b1f3c
493ac2c5-ca7d8d80
Compiler	MSVC 2017 (PGO)

Removed all extensions, set up a new person, the problem remains the same. The stable Chrome version works as usual.
Now I deleted all data, cookies, history etc etc on the Canary version, problem still exists.
When I'm logged in, I can open new pages and open gmail as intended. As soon as I close the browser and start it again, I get directed to the page where I can either log in or create an account and have to type everything in it.

Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

Unable to reproduce this issue on canary 65.0.3294.3 using windows 10 with steps mentioned in comment#0 and comment#2. Attaching screencast for reference.

@Reporter: Could you please try un-installing and installing canary freshly and check the issue. You can download canary from https://www.chromium.org/getting-involved/dev-channel. Please report us back the result. This would help in further triaging of the issue.

Thanks!

Hi,

I tried everything. Uninstalled, installed, new profile, old profile, cookies, browser history, it does not keep me logged in and with the latest version (downloaded 2 hours ago) nothing changed. My account name and password are not getting stored. Whenever I open it, it seems like I opened the page it for the first time.

Regular Chrome works perfect.

Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

Unable to reproduce this issue from TE end. Hence removing Needs-Bisect label. Please feel free to add back if required

Could someone from Gmail team take a look into this issue.

Thanks!

alexandra.winkler2008: We would need more information in order to debug the issue:

1. What account are you trying to connect with? Is it a gmail.com account? Or is it an enterprise / managed account?

2. Could you please record your screen while you start Chrome if this occurs again? We're working on a force sign-in policy at start-up (https://bugs.chromium.org/p/chromium/issues/detail?id=175880 ), so maybe you are hitting this.

3. After you start Chrome, may I ask you please open chrome://signin-internals, take a screenshot and attach it to the bug?

1) its my private googlemail.com account and some friends that are using Canary too, have the same problem as we figured out today.

2) This is part of my link to login and this works on explorer, Firefox and regular Chrome. https://mail.google.com/mail/u/0/?hl=censored=1#inbox

as soon as I press enter on Canary, it switches to  https://www.google.com/intl/de/gmail/about/#

3) Screenshot attached

Deleted: bug.JPG 186 KB

	bug.JPG 186 KB View Download

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

alexandra.winkler2008: This is a real unexpected state - there are in fact no Google accounts in your cookies.

Could you please try doing the following and let me know what you get:
1. Open chrome://flags/#account-consistency
2. Change the value to "Enable DICE (fix auth errors)"
3. Restart Chrome and resign in to Gmail
4. Restart Chrome again and check again that you are signed in to Gmail.

Also, could you please take a screenshot of chrome://settings/content/cookies?search=cookie ?

Did 1-4, problem remains the same. 

Screenshot attached.

Deleted: bug.JPG 32.6 KB

	bug.JPG 32.6 KB View Download

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

And I suppose this is a Gmail only issue, right? Do you continue to be signed in for other websites?

Its a Gmail - Canary issue. I stay signed in at Gmail on all other browsers and yes, I stay signed in on other websites like Facebook or other email accounts.

alexandra.winkler2008: We'd like to see what is going on on the Google auth server. For this we'd need your help a bit more help (thank you so much for helping us track down this bug).

1. Open https://accounts.google.com/ReportBug on the Canary where you hit the bug.
2. Reproduce the bug once.

We also need your explicit permission to check the sign-in and sign-out events for accountalexandra.winkler2008@googlemail.com for the recent events coming from this device. Do you have your consent to check the recent sign-in and sign-out events for account accountalexandra.winkler2008@googlemail.com?

1+2 done.
And you have my explicit permission to check the sign-in and sign-out events of my account alexandra.winkler2008@googlemail.com

alexandra.winkler2008: Thank you so much for filing the bug and for helping us debuggging it. We'll let you know what we find.

alexandra.winkler2008: Could you follow the steps below one more time? We would need the number on /ReportBug to debug issues. Thanks for keep reproducing on Canary and help us debug :)

1. Open https://accounts.google.com/ReportBug on the Canary where you hit the bug. Note down the number displayed on the page and provide us the number.
2. Reproduce the bug more one time.

Number 24496673
reproduced bug

Thanks for helping me :)

Adding Network and Signin components.

It looks like after Chrome Canary (65) restart, the user cookies under accounts.google.com and .google.com are cleared from browser (however cookies for other websites are still present per comment #20 ).

From the server log, user was able to sign into Gmail on a clean cookie jar initially. When user attempted to sign into Gmail again (after canary restart), there are no cookies present in the login request. And there is no request to the logout endpoint to expire cookies neither.

alexandra.winkler2008@googlemail.com: I am wondering if you have an extension that is clearing these cookies. Could you please go to chrome://extensions/ and disable all extensions and try reproducing the bug?

I already tested that at the beginning and only reactivated Google drive and Google docs. Deactivated both again and the problem still exists.
On the stable version I have all extensions (9) running without a problem.

We cannot really explain why only the Gaia cookies are lost when you restart the browser. There is a different bug https://bugs.chromium.org/p/chromium/issues/detail?id=795827 where Chrome fails to load all cookies and we suspect that may be due to the fact that Chrome cannot decrypt the cookies when it starts.

As we cannot reproduce, it is hard to explain what is going wrong here. Just to make sure there is not some other software that clears the Chrome profile folder, may I ask you to try the following:
* create a folder on the local drive
* start Chrome Canary using that local drive with instructions here https://chromium.googlesource.com/chromium/src/+/master/docs/user_data_dir.md#command-line

Can you still reproduce the bug in this configuration?

Adding rdsmith as well, since this is about cookies.

alexandra.winkler2008@googlemail.com: We had a similar bug report from another user and we managed to debug it (Issue 797800). That issue turned out to be an encryption problem and rebooting the computer solved it.

Just to double check if this is the same root cause, may I ask you do the the following:
1. Download latest Chrome Canary (this is important as the new Canary has additional logging added).
2. Start Chrome Canary again with logging enabled: command line arguments "--enable-logging --vmodule=token_service_table=1,mutable_profile_oauth2_token_service_delegate=1"
3. Sign in to Chrome.
4. Take a screenshot of chrome://signin-internals
5. Quit Chrome Canary.
6. Send me the logs from %LOCALAPPDATA%\Google\Chrome SxS\User Data\chrome_debug.log and the screenshot from step 4.

Also, please restart Chrome and see if you still reproduce the issue. Let me know if you still hit this problem.

I wanted to pipe in and let you know that I've been experiencing very similar issues.  I was going to create a new bug but I saw this one and decided to add to it.  I can create a new bug report if required.

I am on Version 65.0.3322.3 (Official Build) dev (64-bit).  I usually run the dev channel builds of chrome to try and help find bugs.  Chrome updated a few weeks ago and I've experienced these issues since over multiple updates over the last few weeks.  However, I get logged out of every website I'm in.  Google accounts, facebook, twitter, reddit etc...  If there is any way I can help, please let me know and I will get you any information that I can.

comment 33: it could be  issue 800414  causing it to fail to save some cookies to the disk when closing the browser

i have that problem with chrome beta and newer and found that when i ran chrome with --enable-logging from the command line, i get the same log messages as mentioned in that issue ("Cookie sqlite error 1555, errno 0: UNIQUE constraint failed"), and i bisected to https://crrev.com/c/775606 which was also mentioned later in a comment on that issue (though versions before that commit still show significantly fewer of the log messages, they still stay logged in to sites)

i'm also not sure if i should open a new issue since that issue already tracks the cause of the problem i have

huglovefan1998@gmail.com: I think the your issue if different than this one as yours only affects cookies, and the current one also affects tokens used for sync.

just received the update to Version 65.0.3325.18 (Official Build) dev (64-bit).  The issue seems to still persist.  There is slight improvement, reddit stays logged in, whereas it did not before.  All google sites, facebook, and twitter all log out when chrome is exited then re-launched.

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

commit e6515d6ae158f5b53b8ee697cdd99d714a8ab402
Author: Randy Smith <rdsmith@chromium.org>
Date: Sat Jan 27 03:57:32 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-Commit-Position: refs/heads/master@{#532152}
[modify] https://crrev.com/e6515d6ae158f5b53b8ee697cdd99d714a8ab402/net/url_request/url_request_http_job.cc

Unable to repro the issue from TE end on reported chrome/chromium version 63.0.3239.84. As per comment# 2, 7 & 10, we haved worked on this issue earlier and unable to reprodue it at that time, hence we cannot confirm that the fix is landed on 66.0.3334.0(latest canary).

@Reporter:
Could you please help in verifying the fix from your end, you can download the latest canary from URL provided, URL: https://www.google.com/chrome/browser/canary.html

Thanks!

i have the same problem for two days now .. i did everything the others did .. cleaning history , cookies , cache , etc .. un-install and re-install Google Chrome .. keeps logging me out .. hoping for a quick fix !!!
p.s the problem persisted on Google Canary which some Google Tech advised to download.

 Issue 805339 ,  issue 806594 ,  issue 806605 , and  issue 806662  might be a duplicate of this one.

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

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

I downloaded the newest version of Canary today and the problem is gone, thank you all very much.

For the record - the download I did before was last Saturday and that one did not solve anything.

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)