We've had performance regressions at sign in/out which have increased the time to logout and back in by several seconds. We've tracked these to several issues. This is the meta bug that is being used to track all of them.

 

We've had performance regressions at sign in/out which have increased the time to logout and back in by several seconds. We've tracked these to several issues. This is the meta bug that is being used to track all of them.

There are multiple separate issues about this:
1. Recent change in cryptohome encryption method from ecryptfs to ext4 crypto. The latter requires "drop caches" every Sign Out, and this causes Chrome to load the whole binary from disk rather than from cache in RAM ( crbug.com/703307 )
2. Old change in kernel related to display/screen initialization. This change caused acquiring/releasing framebuffer takes much longer so everytime Chrome restarts there is a long black screen delay ( crbug.com/705159 ).
3. If there is custom flag change, Chrome restarts itself during Sign In. This causes black screen delay right after a user authenticates. (crbug.com/681278).
 

We've had performance regressions at sign in/out which have increased the time to logout and back in by several seconds. We've tracked these to several issues. This is the meta bug that is being used to track all of them.

There are multiple separate issues about this:
1. Recent change in cryptohome encryption method from ecryptfs to ext4 crypto. The latter requires "drop caches" every Sign Out, and this causes Chrome to load the whole binary from disk rather than from cache in RAM ( http://crbug.com/703307 )
2. Old change in kernel related to display/screen initialization. This change caused acquiring/releasing framebuffer takes much longer so everytime Chrome restarts there is a long black screen delay ( http://crbug.com/705159 ).
3. If there is custom flag change, Chrome restarts itself during Sign In. This causes black screen delay right after a user authenticates. (http://crbug.com/681278).