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

Issue 839710 link

Starred by 2 users
Status: Fixed
Owner:
█ rjwright@chromium.org
Last visit > 30 days ago
Closed: May 2018
Cc:
nverne@chromium.org
tbuck...@chromium.org
benwells@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Crash when cancelling setup flow

Project Member Reported by tbuck...@chromium.org, May 4 2018 
Chrome version: 68.0.3416.0 dev
OS: Chrome

Repro steps:
1. Start Linux setup flow from chrome://settings
2. Click cancel

Expected: setup cancels
Actual: crash

Comment 1 by rjwright@chromium.org, May 7 2018

Cc: rjwright@chromium.org
Repro'd when cancelling during "Starting Termina VM" step. Haven't got a proper stack trace yet. Shall I take a look at this one?

2018-05-07T16:54:35.282016+10:00 INFO vm_concierge[6794]: Started VM with pid 6
2018-05-07T16:54:35.282467+10:00 INFO kernel: [  767.363907] chrome[5694]: segfault at 2010e29 ip 00005d04a5dc4524 sp 00007ffd82451660 error 4 in chrome[5d04a4977000+796c000]
2018-05-07T16:54:35.286856+10:00 INFO crash_reporter[6836]: libminijail[6836]: mount /dev/log -> /dev/log type ''
2018-05-07T16:54:35.305148+10:00 WARNING crash_reporter[6836]: [user] Received crash notification for chrome[5694] sig 11, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)

Comment 2 by benwells@chromium.org, May 8 2018

Cc: -rjwright@chromium.org benwells@chromium.org nverne@chromium.org
Owner: rjwright@chromium.org
Just chatted to Nick, please have a look. Speak to Nick if you need help!

Comment 3 by rjwright@chromium.org, May 9 2018 

This crash happens 100% of the time when you cancel in the "Starting Termina VM" step. It does not happen in the "Loading component" step.

The crash does not show up in chrome://crashes.

I've been trying to get a proper stack trace for it. Installing Chrome with --nostrip doesn't yield a stack trace (and it actually suppresses the segfault message).

Next step is to get the stripped segfault message and try to re-symbolize it.

Comment 4 by tbuck...@chromium.org, May 10 2018

Labels: Hotlist-Crostini-UI

Comment 5 by nverne@chromium.org, May 14 2018 

I just submitted a CL that incidentally fixes this bug. (It wasn't the main focus of the CL). 

https://chromium-review.googlesource.com/c/chromium/src/+/1051208

Comment 6 by nverne@chromium.org, May 14 2018

Status: Fixed (was: Assigned)

Comment 7 by vapier@chromium.org, May 17 2018

Labels: -Restrict-View-Google
►

Sign in to add a comment