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

Issue 779311 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 771345



Sign in to add a comment

Setting wallpaper is delayed for several seconds at login screen

Project Member Reported by wzang@chromium.org, Oct 28 2017

Issue description

Chrome Version: 64.0.3251.0

At login screen, when switching between the user pods, the wallpaper update is delayed for several seconds. 

Also, during the log in, the wallpaper is 'stuck' for a noticeable amount of time before entering the active user session. (See video)



 

Comment 2 by wzang@chromium.org, Oct 28 2017

Cc: alemate@chromium.org jdufault@chromium.org x...@chromium.org
Do you have an any idea what may cause this?

Comment 3 by x...@chromium.org, Oct 30 2017

Owner: wzang@chromium.org
I think you can do a bisect to identify which CL caused this problem. 

Comment 4 by x...@chromium.org, Oct 31 2017

Cc: krajshree@chromium.org brajkumar@chromium.org ajha@chromium.org
 Issue 779995  has been merged into this issue.

Comment 5 by x...@chromium.org, Oct 31 2017

Labels: M-64 ReleaseBlock-Beta
Add labels from  Issue 779995 

Comment 6 by x...@chromium.org, Nov 2 2017

Cc: -x...@chromium.org -ajha@chromium.org wzang@chromium.org
Owner: x...@chromium.org
Let me do the bisect.

Comment 7 by x...@chromium.org, Nov 2 2017

Cc: ajha@chromium.org
oops. Add the cc back. 

Comment 8 by wzang@chromium.org, Nov 2 2017

Cc: -ajha@chromium.org
I did an initial bisect and the bad commit is between:

Known to be good: ab7f6879b56532d0e1fbe42db3907ee6f478f465

Known to be bad: 9bce89359c786654e07c1b5017c8514d1875c206


However it's hard to go further because lots of commits in between suffers from a crash at startup, and there doesn't seem to be anything suspicious by only looking at the logs.

Comment 9 by wzang@chromium.org, Nov 2 2017

Cc: ajha@chromium.org
So I suggest to find the crash commit first?... Also, this is not reproducible on a Linux build, but only on a device. 
Correct of #8:

Known to be bad: ab7f6879b56532d0e1fbe42db3907ee6f478f465

Known to be good: 9bce89359c786654e07c1b5017c8514d1875c206


Comment 11 by x...@chromium.org, Nov 2 2017

Great! Thanks. I'll start from where you left. Probably have to find the crash first.

Comment 12 by x...@chromium.org, Nov 3 2017

Cc: x...@chromium.org
Owner: mcasas@chromium.org
Status: Assigned (was: Untriaged)
Bisect is done. This is the culprit CL https://chromium-review.googlesource.com/728325. Assign to the CL owner for further investigation.

(Btw: During bisecting, Chrome can't start because of the CL: https://chromium-review.googlesource.com/c/chromium/src/+/736834. Revert this CL before bisecting)
Blocking: 771345
Project Member

Comment 14 by bugdroid1@chromium.org, Nov 7 2017

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

commit 8ba32f975545211716e05cc4ce70113ba3136532
Author: Miguel Casas-Sanchez <mcasas@chromium.org>
Date: Tue Nov 07 05:03:34 2017

ui/display: add flag to enable use of monitor's color space info

This CL adds a new flag to control if the monitor's provided color
space info is actually propagated at the DisplayManager level, and
also surfaces this flag in chrome://flags. The flag is disabled by
default and the chrome://flags entry allows for enabling it. This
flag will help debug the possibly related  issue 779311 .

Bug:  771345 ,  779311 
Change-Id: I6df69c5fb9ab9954e9ff9f4fc04fe0616594315c
Reviewed-on: https://chromium-review.googlesource.com/754593
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514398}
[modify] https://crrev.com/8ba32f975545211716e05cc4ce70113ba3136532/chrome/browser/about_flags.cc
[modify] https://crrev.com/8ba32f975545211716e05cc4ce70113ba3136532/chrome/browser/flag_descriptions.cc
[modify] https://crrev.com/8ba32f975545211716e05cc4ce70113ba3136532/chrome/browser/flag_descriptions.h
[modify] https://crrev.com/8ba32f975545211716e05cc4ce70113ba3136532/tools/metrics/histograms/enums.xml
[modify] https://crrev.com/8ba32f975545211716e05cc4ce70113ba3136532/ui/display/display_switches.cc
[modify] https://crrev.com/8ba32f975545211716e05cc4ce70113ba3136532/ui/display/display_switches.h
[modify] https://crrev.com/8ba32f975545211716e05cc4ce70113ba3136532/ui/display/manager/display_manager.cc

Status: Fixed (was: Assigned)
This should be fixed now. Anyone would like to Verify? Thanks

Comment 16 by x...@chromium.org, Nov 7 2017

Just tested on my device and verified this issue is fixed. Thanks!

Sign in to add a comment