1: was login done in classic ash?
2: the --mash in chrome://flags triggers a reload of chrome, did this bring up the mash login screen?
3: does QuickLaunch work? Can you bring a chrome window back up?

I haven't loaded device in a while, so haven't seen this myself.

With setting --mash via about:flags, the login should be done in classic ash. Upon login, user flags are applied and chrome will be restarted with --mash (and --login-user to run in a logged in state).

1. First login was classic ash.
2. Then I flipped the flag, which restarted the browser (without signing out). That time the browser came up, with the content area too small ( issue 682810 ).
3. I powered off by hard-power-down (hold power for 15 seconds, since ash doesn't respond to power button today)
4. On reboot the screen is white

I don't know if quick launch works. Once I'm in this state I have to re-image the device to wipe the --mash flag, so it takes a while.

This is not 100% consistent. Once I saw the top-left 1/4 of the login screen.

No crash stack trace in /var/log/ui/ui.LATEST
Nor any obvious error message, tons of expected "Not implemented" messages though.

I am seeing multiple chrome processes, like with  issue 683192 .

Killing one at random flashed the login screen. Makes me wonder if the first chrome instance being initialized is creating the login screen. Then the second one coming up steals the foreground.

So after deploying to R58.0.2991.0 (9198.0.0) the login screen comes up as expected. Login brings us to the desktop. 


However this still fails on a hard power cycle. When that occurs I'm seeing a crash on Shell::GetInstance, I'll hunt down the root cause

The root cause for this is the same as one blocking  issue 682804 .

kylechar@ has a patch up with resolves the issue for both: https://codereview.chromium.org/2648433006/

Another case of chrome/browser trying to directly access the Shell