Sync stops on performing chrome://restart
Reported by
aiman.an...@etouch.net,
Feb 9 2018
|
|||||||||
Issue descriptionChrome Version: 66.0.3343.3 (Official Build) Revision e1f2ec046b66d1e2cd4ce82fecff22dad160fd54-refs/branch-heads/3343@{#4} (32/64-bit) OS: Mac(10.13.1, 10.13.4). Steps to reproduce: 1.Launch Chrome, go to chrome://settings and sign in to chrome with an account that does not have sync passphrase. 2.Restart the chrome using chrome://restart. 3.Observe the sync section on chrome://settings/people. Actual Result: Sync stops on performing chrome://restart. Expected Result: Sync should work properly on performing chrome://restart. This is Non-regression issue seen from ‘M-61’ build #61.0.3113.0 Note: 1. Issue is also reproducible on Stable #64.0.3282.140, Beta #65.0.3325.51 and Canary #66.0.3344.0 build. 2. Issue is not reproducible on Mac (10.12.6), Win(7,8,8.1,10) and Linux (14.04 LTS)
,
Feb 12 2018
,
Feb 26 2018
--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
,
Feb 26 2018
Mihai, can you take a look at this? It looks like we're losing the LST when Chrome is restarted via chrome://restart. While I'm not particularly concerned about that scenario, I'm wondering whether that might also happen in other scenarios where Chrome gets shut down in a weird way?
,
Feb 28 2018
iman.ansari@etouch.net: May I ask you to repro it and then open chrome://signin-internals and attach a screenshot to this bug?
,
Mar 7 2018
Hi, w.r.t. comment #5, Retested the above issue on Canary build #67.0.3362.0 for Mac(10.13.1,10.13.4) and unable to repro the issue now, Sync is working properly on performing chrome:/restart. Attaching screen-cast for reference. Thank You!
,
Mar 7 2018
aiman.ansari@etouch.net: Maybe this was just a flake (somehow we could not encrypt the token before saving it to disk). As it is fixed in M67, maybe we need just to retest it once beta is out again.
,
Apr 6 2018
--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
,
Aug 1
,
Sep 3
--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 |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by rbasuvula@chromium.org
, Feb 9 2018