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

Issue 869267 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

CrOS crash after opening system settings.

Reported by kamil.ch...@displaylink.com, Jul 31

Issue description

Chrome Version: 69.0.3496.0
Chrome OS Version: 10894.0.0 canary-channel link
Chrome OS Platform: link

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Open System settings.

Expected Result:
System settings opens correctly.

Actual Result:
OS crashed and web browser is open on default starting page.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
User cannot change via UI settings.

Please provide any additional information below. Attach a screen shot or
log if possible.
Issue is also seen on chell Chromebook.
Issue is also reproducible on dev channel 69.0.3497.0.
Issue is not reproducible on beta channel 68.0.3440.76.
I have tried to narrow down the issue on the internal build chromium images and it appears that issue was introduced between 20th (midnight) and 23th (noon) of June CEST.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
 
Labels: Needs-Feedback
Please provide the crash report id from chrome://crashes
Under chrome://crashes there are no crashes stored (automatic crashes report are enabled). I have reproduce issue few times.
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 1

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: bhthompson@chromium.org
Labels: -Pri-3 ReleaseBlock-Stable M-69 Pri-2
I tried this with both a logged in user and guest and was unable to reproduce on:

samus running canary (10925) 
caroline running beta (10718.63)

Moving the caroline to dev I had more luck. A caroline running dev (10895.10) with guest mode exhibits this, logging in as a normal user does not.

This repros both from the gear button from the clock menu, and navigating to about://settings directly.

This seems to qualify as an RBS.

I am not sure if it is a real crash or something else, it certainly kills the active window of tabs, but I never see anything in about://crashes maybe the guest user does not generate crash reports?
Components: UI>Settings
Cc: abodenha@chromium.org
Cc: steve...@chromium.org
Labels: -Pri-2 Pri-1
Can this still be repro'd? 10895.10 is chrome 69.0.3497.21 (chrome revisions are much more useful for chrome crashes :)), which is about 20 revs behind.

I can't repro this on on ToT samus. I don't have a caroline here. I can get one from home and re-image it, but it would be great if we can verify this on a more recent build.

I realize I have a kevin device, not caroline. It does not crash on 69.0.3497.35.

I will see if I can scrounge an arm based device in case that's related.

Status: WontFix (was: Unconfirmed)
I cannot repro on 10895.21 69.0.3497.35 with a Caroline, so it appears this may have been fixed by something else. 
And I just confirmed that I can repro on coral @ 69.0.3497.21 but can not repro on coral @ 69.0.3497.43, so doubly confirmed fixed :)

Sign in to add a comment