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

Issue 712764 link

Starred by 2 users
Status: Closed
Owner:
jdufault@chromium.org
Closed: Nov 19
Cc:
█ alberto@chromium.org
█ zelidrag@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

ChromeOS resume-from-suspend feels longer than it used to be

Project Member Reported by w...@chromium.org, Apr 18 2017 
Chrome Version: 59-ish
OS: ChromeOS (observed on Pixel v1)

What steps will reproduce the problem?
(1) Sign-in to ChromeOS.
(2) Close the lid and wait for the device to suspend.
(3) Re-open it and wait for the sign-in prompt.

What is the expected result?

Expect that the sign-in prompt appears almost instantaneously.

What happens instead?

Sign-in prompt takes ~3s to appear, on my Pixel v1.

On another device (lower-end Chromebook) I've noticed that the system is janky for a while immediately after un-locking the device after resume, suggesting that the system is busy doing something.

Unfortunately this is purely qualitative; I've not yet found concrete data to indicate if/where there is an issue. :(

Comment 1 by w...@chromium.org, Apr 18 2017

Cc: alberto@chromium.org zelidrag@chromium.org
+zelidrag, alberto: I took a chrome://tracing trace across a sleep/resume cycle to see if it captured anything interesting - who should take a look at this?

Comment 2 by nduca@chromium.org, Apr 20 2017

Labels: Performance-Responsiveness

Comment 3 by pbe...@chromium.org, Apr 21 2017

Owner: r...@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by r...@chromium.org, Apr 24 2017

Owner: jdufault@chromium.org
James, do you think this is this a regression? Or did it always take this long.

Comment 5 by zalcorn@chromium.org, Nov 19

Status: Closed (was: Assigned)
This was very much improved with Views login and lock, going to close this one.
►

Sign in to add a comment