New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 761180 link

Starred by 8 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 703307
issue 761135



Sign in to add a comment

Sign-out takes too long

Project Member Reported by zalcorn@chromium.org, Aug 31 2017

Issue description

Using this as the canonical bug for delay and black screen during sign-out. 
Right now it is approaching 9 seconds on some devices, we should get it down to a much more reasonable number.
 

Comment 1 by r...@chromium.org, Aug 31 2017

Cc: -sonnysasaka@chromium.org r...@chromium.org abodenha@chromium.org
Labels: ReleaseBlock-Stable M-61
Owner: sonnysasaka@chromium.org
Potentially related issue with guest mode: crbug/761181
zalcorn@ Can we dupe this one to that bug?

Comment 4 by zalcorn@google.com, Sep 5 2017

I'd prefer not to as the other one may not be related and is not RBS like this one is.
Cc: cywang@chromium.org bccheng@chromium.org
Cc: cros-perf-detectives@google.com
We have a boot test that also measures shutdown time. Not sure how similar the code path is between sign-out and shutdown, but please take a look at the graph first to see if it tracks the sign-out time:

https://chromeperf.appspot.com/report?sid=edb0654f79120aef0ffd7548db18eb2a748d239e34a28c5af40df0be50efd341

With the above link you can add more boards and compare the results.
bccheng@, I cannot load the above graph. Do I need specific permission?
There is "sign in" button at the top right corner. Could you double check if you are signed in?
Ah I see, I can see the graph now. There are differences between sign out and shutdown so we cannot 100% rely on shutdown metrics to investigate sign out. Is there a plan to record Sign Out metrics also? We have been having sign out regression since months ago and I think it will be useful to record this as perf metrics.
Re #9: as far as I understand, chrome perf can only measure in-process time, i.e. it doesn't support measuring time from "user clicked on restart button in one chrome process", chrome restarted, and "some UI was shown in another chrome process".
Blockedon: 703307
Labels: -ReleaseBlock-Stable
After talking with rkc@ it sounds like this is a combo of a crash on shutdown that's been fixed combined with  bug 703307 . Given that, I'm removing RBS for this.
Blockedon: 761135
Project Member

Comment 15 by bugdroid1@chromium.org, Sep 28 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/fed466c8b2c61dbc08592774567d5a4e9a657cc8

commit fed466c8b2c61dbc08592774567d5a4e9a657cc8
Author: Chung-yih Wang <cywang@google.com>
Date: Thu Sep 28 06:52:14 2017

Add platform_LogoutPerf into ebuild

The platform_LogoutPerf test is for measuring the time elapsed for
logging out a GAIA user session.

BUG=chromium:761180
TEST=test_that DUT_IP platform_LogoutPerf
CQ-DEPEND=CL:670804

Change-Id: Id60186160b1ea6e90d7881dedd60e1cc2a912412
Signed-off-by: Chung-yih Wang <cywang@google.com>
Reviewed-on: https://chromium-review.googlesource.com/670805
Reviewed-by: Ben Cheng <bccheng@chromium.org>

[modify] https://crrev.com/fed466c8b2c61dbc08592774567d5a4e9a657cc8/chromeos-base/autotest-chrome/autotest-chrome-9999.ebuild

Cc: sonnysasaka@chromium.org
Components: -UI>SignIn
Labels: -Pri-1 -M-61 Hotlist-auth-polish Pri-3
Owner: ----
Status: Available (was: Assigned)
I very very much want to make improvements here, but it's clear this isn't straightforward and isn't time sensitive, so P3 available for the moment.
 Issue 712897  has been merged into this issue.

Sign in to add a comment