Additional note: the user has a ton of extensions, so I disabled all extensions (but not uninstalled), closed and restarted and got the same result (twice), so it doesn't seem to be extension related.

--Chrome Identity automated triaging--

This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

I can confirm this is still a problem, just didn't have time to investigate more. This is on a brand new Surface Book 2.

maruel@: Sorry for missing this report before. On restart, could you please take a screenshot of chrome://signin-internals and attach it to this bug?

This may be an issue with Chrome failing to descrypt the tokens db.

--Chrome Identity automated triaging--

This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

Sorry for no update, I've been extremely busy.

It is still happening. But if it were a general problem we'd hear more outrage. On the other hand the fact that it happened on a brand new installation is concerning. Will submit a screenshot soon.

I do not see any issue from the screenshot that you shared. From your description, it is not clear to me if this is a profile order problem or a sign-in problem. In your scenario, you have 2 profiles: profile 1 signed in and profile 2 signed out. They both are open and load the same page (google.ca). You close profile 2, then profile 1 and then restart Chrome. And Chrome starts with a profile that is unsigned. Is that Profile 1 or Profile 2? If on start-up you get Profile 2, then this is just a problem of Chrome starting with the wrong profile (and not a sign-in issue).  

Only the first profile fails, the one starting with "josee.". All other profiles are fine.

Chrome Sign-in works (sync, extensions, etc), it's the actual cookies that fails. So if she closes the whole profile and opens it again and navigate to gmail.com, she's logged out, even if she is logged in into Chrome.

I tried:
- Disabling all extensions
- Deleting the profile and recreating it

This baffles me and I'm not sure where the problem lies as other profiles are fine; they stay logged in into gmail if I close the profile window and open it back. That's not the case for the profile #1.

One interesting bit:
- If I visit google.ca instead of gmail, I do see the profile's icon, as if it were in an "half-logged in" state.

Is this only gmail? If not, then there was an issue with cookies being lost on each Chrome start-up: https://bugs.chromium.org/p/chromium/issues/detail?id=795827 

Yeah looks like it. Thanks for the investigation. She's now on 65.0.3325.181. Hopefully it'll resolve by itself.