Somewhat similar issues reported on 71.0.3578.27 beta. Users report being unable to sign in from Login screen (crashes, get a black screen), and then having to sign in as a Guest instead.

Reports with logs:
https://listnr.corp.google.com/report/85756717687
https://listnr.corp.google.com/report/85756215606
https://listnr.corp.google.com/report/85752886744
https://listnr.corp.google.com/report/85756454116

See also:
https://listnr.corp.google.com/report/85756480886
https://listnr.corp.google.com/report/85756432894
https://listnr.corp.google.com/report/85756346184
https://listnr.corp.google.com/report/85756291241
https://listnr.corp.google.com/report/85755669683
https://listnr.corp.google.com/report/85755670375

Same thing happening to my Acer Chromebook 14 (CB3-431) after yesterday's update to 71. Performed a hardware reset (refresh key + power key). Added a second profile and I can get Chrome OS to start.  Guest mode works as well.  Just cant log in with my primary profile and this is the only machine I have.

INFO:
Platform
11151.17.0 (Official Build) beta-channel edgar

Firmware
Google_Edgar.7287.167.132

Channel
Currently on beta

ARC Version
5090785

Blink
537.36 (@d7850e07856a010c464bc7ea52e4ee10ca5965ce)

V8
7.1.302.11

User Agent
Mozilla/5.0 (X11; CrOS x86_64 11151.17.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.27 Safari/537.36

Build Date
Tuesday, October 30, 2018

Deleted: Screenshot 2018-11-01 at 9.17.30 AM.png 366 KB

	Screenshot 2018-11-01 at 9.17.30 AM.png 366 KB View Download

Do we have any crash reports/stack traces?

Possible duplicate of issue 899910

I'm unable to repro so far; from logs I can see that the browser process is exiting with signal 11 (segfault)

Just happened for a second time, sent feedback from guest mode at 14:20 EST with the bug number and "#wtlm-feedback-900548". I also found that the feedback wizard is refusing to open even when pushing the key combo multiple times.

Deleted: debug-logs_20181102-141856.tgz 1.8 MB

debug-logs_20181102-141856.tgz 1.8 MB Download

Re #10, do you see a crash in chrome://crashes? If you do can you post the crash ids?

Yes, there are two which were uploaded on October 31:

8e7ca56ebf8f70f0
008b0ae4f9f593ec

Tried to reproduce this on M72 with failure, however I did get a Sign-in error message which has been happening since M70 dev. I'll let you know if I can reproduce it again.

Same problem since update to 71.0.3578.27 official build Beta 64bit
Log-in fails, screen attempts to behave correctly but returns, as in a loop.
Checked password and keyboard.
Will not Powerwash yet in case solution is eventually found.

This could be issue 895589 [1]. Unfortunately the crashes in comment #12 have garbled stack traces.

1: https://chromiumdash.appspot.com/commit/aac775224f831c911c2bc4ef0ae46f2a90b19d62

Re #15, could you go into guest mode or other user profile and get the information asked in #11? Possibly there is something there that could be used.

<Bulk edit> Reminder M71 Stable is approaching. Please review this bug and assess if this is indeed a RBS. If not, please remove the RBS label. If so, please make sure any planned work will be tested in Beta and verified before the Stable date. Thanks

<BULK EDIT> Reminder we nearinf M71 Stable. Please review this issue and update with your plan on next actions. Thanks.

 Issue 890167  has been merged into this issue.

May be related:  crbug.com/870838 

[Adding content from  crbug.com/890167 ]

ChromeOS version: 10895.56.0/69.0.3497.95
ChromeOS device model: HP Chromebook 14 G5(snappy)/HP Chromebook 11 G5 EE (relm)
Case#: 17030823

Description:

Customer is having troubles when signing in with his account to any chromebook.  

Customer sign in to the chromebook and the first thing that happens is a black screen, after that the browser shows up saying that chrome crashed and to recover tabs but before customer can even do anything the system shows another black screen and then it end the session and customer is back to the login screen. 


Steps to reproduce: 

1) sign in to the chromebook
2) black screen pops out
3) browser shows up saying that chrome crashed and to recover tabs 
4) another black screen
5) end of session for the user, back to login screen

Current Behavior / Reproduction: 

1) sign in to the chromebook
2) black screen pops out
3) browser shows up saying that chrome crashed and to recover tabs 
4) another black screen
5) end of session for the user, back to login screen

Expected Behavior: 

Should work fine after login

Drive link to logs: https://drive.google.com/drive/folders/1gaSRmBb77hEpEXJI1MX3vZpTFiO9LdV1?usp=sharing

Given those logs are from 69 that's most likely a different crash - this one surfaced in 71. I also didn't see anything useful in the logs unfortunately since they don't include anything that happened after logging into the session.

Sent feedback a few minutes ago with "#wtlm-feedback-900548" in the last line. Couldn't attach debug logs to the feedback, so I attached them here.

Deleted: debug-logs_20181121-085824.tgz 4.4 MB

debug-logs_20181121-085824.tgz 4.4 MB Download

Recorded it, see the video here:
https://photos.app.goo.gl/4kKF5Ry4rzmZkZDQ9

Been a while since updates and this is tagged as a RBS.  Please reconsider the tag, fix, etc.  Thanks

Looks like this is getting tracked by http://b/119697372. Trying to see if this is still an issue on more recent M71 Beta builds. Looking for user reports on versions newer than 71.*.27?

Thanks for the update.  Please note that b/119697372 is tagged as nocturne only, whereas this is for other(s).  Possible for  willlandrieu@ to retest with last week's beta, or later?

This is almost certainly a dup of b/119697372, closing as such.

#28, I have not run into any issues on any of the beta builds as well as dev and canary although I will let you know if anything comes up.

I just got this again on M72 dev (platform 11316.18.0-18.12.12) on peppy, sent a bug report (from willlandrieu@) after reproducing  issue 870838  linking the similar crash behavior seen in comment 25. I signed out of the account and tried signing in again and got the bug, I'll try to send debug logs, but they may not have the details you need to investigate.

Customer reporting this issue in 71.0.3578.94, b/ was closed as WontFix as well, this is definitely not the kind of issue we should be not fixing, as it makes Chromebook unusable. And this crbug would useful for tracking customer issues anyway.

A stable refresh is pending so if there's going to be a fix it should be soon (and verified as a fix).  I won't be able to take the merge without verification on ToT, M72 or similar across devices.  Were any dumps collected in feedback reports per #31 and #32?

vkhabarov@, please follow up on the associated b/, not here. b/119697372 has much more recent investigation.

I'm not seeing many user reports about crashes from Login screen. 

Though I am seeing some customer reports on recent M71 builds (71.0.3578.98 & 71.0.3578.94) about users being unable to login and having to sign in as guest instead. Seems like a different issue.

#33, If there were any from #31, then they are most likely gone locally since I powerwashed the device to clear the issue. I'll let you know what I add to the report if the issue surfaces again.

#35, that could be because they do not know how to submit a feedback report or that they could make one from the sign in screen (I did not know that until another PE told me about it.)