Blur causes significant slowdown on first display of views-based lock screen |
||||
Issue description
Adding a background blur to the lock screen makes the first display take
significantly longer, ie, from nearly instant to a very visible 2+s load.
Showing the lock screen is very quick after the first slow run.
The code to activate the blur is essentially:
views::Widget* window = ...;
window->GetLayer()->SetBackgroundBlur(10);
The blur value (10) does not appear to make a difference.
,
Jun 20 2017
On kevin, it is about 30-100ms to show blurred lock screen. Without blur, it is about 25-40ms. If you can finish the code to allow unlock in the show-md-login mode, I can do more tests.
,
Jun 20 2017
Do you have animation when showing the show-md-login lock_screen?
,
Jun 26 2017
We may or may not keep the existing animation, which iirc is all of the windows flying to the edges of the screen. Ideally we would not need one, or it could be very short.
,
Jun 30 2017
I can see the animation now, it seems expanding the blur layer from near the bounds to the final full screen.
,
Jun 30 2017
,
Dec 4 2017
The lock screen becomes opaque when this is tested on a pineview based board dell 2110 which has intel atom n470 processor with an Intel GMA3150 gpu. This is a pretty old machine. Can see this opaqueness at the login/lock screen after blur has been enabled in R61 chromiumos.
,
Jan 26 2018
,
Jul 9
Close this for now since it is old. If this is still a problem, please reopen it. |
||||
►
Sign in to add a comment |
||||
Comment 1 by wutao@chromium.org
, Jun 15 2017