New issue
Advanced search Search tips

Issue 778763 link

Starred by 1 user
Status: WontFix
Owner:
abodenha@chromium.org
Closed: Oct 2017
Cc:
allendam@chromium.org
r...@chromium.org
mkarkada@chromium.org
dhadd...@chromium.org
abod...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

User accounts corrupted after AU from M62 beta to M63 dev

Project Member Reported by sdantul...@chromium.org, Oct 26 2017 
Device on M62 build 9901.54.0, 62.0.3202.74 beta channel

Issue seen after AU to M63 10032.17.0, 63.0.3239.20 dev channel

What steps will reproduce the problem?
(1) Device in developer mode
(2) Modify /mnt/stateful_partition/etc/lsb-release as below
    CHROMEOS_AUSERVER=https://omaha.sandbox.google.com/service/update2
    CHROMEOS_RELEASE_TRACK=dev-channel
(3) Connect device to ethernet
(4) Open crosh terminal (Ctrl + Alt + t) and give 'autest' command
(5) After update download, restart device and try login to any of the user accounts


What happens ?
Browser crashes continuously for few times and user is logged out automatically.

Tested on quawks and eve so far and able to repro on both with above steps.

Comment 1 by sdantul...@chromium.org, Oct 26 2017 

Issue exists even after rebooting device.

Logs and video from quawks device: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/778763/

Comment 2 by abod...@chromium.org, Oct 26 2017

Cc: r...@chromium.org abodenha@chromium.org

Comment 3 Deleted

Comment 4 by abod...@chromium.org, Oct 26 2017 

Reproduced on BOB too

Steps:
Device have 9901.54.0 Beta
Change channel at chrome://settings/help from Beta to dev
Reboot the device after successful AU.
Now try to login.

results:
Browser crashes continuously after login.

Comment 5 by abod...@chromium.org, Oct 26 2017 

attached log file.
debug-logs_20171026-134616
1.7 MB View Download

Comment 6 by allendam@chromium.org, Oct 26 2017

Cc: allendam@chromium.org

Comment 7 by josa...@chromium.org, Oct 27 2017

Labels: -Pri-2 Pri-1
Owner: abodenha@chromium.org
Status: Assigned (was: Untriaged)
Is the update to existing dev (	10032.4.0/63.0.3239.7) working fine? 

e.g. just take any device in normal mode and switch to dev channel

Comment 8 by gkihumba@google.com, Oct 27 2017

Owner: abod...@chromium.org
Josafat I think you meant to add abodeti@ as owner.

Comment 9 by sdantul...@chromium.org, Oct 27 2017 

Change channel from M62 beta to M63 existing dev (10032.4.0/63.0.3239.7) works fine. Tested on quawks device.

Comment 10 by abod...@chromium.org, Oct 27 2017

Owner: ----
Not reprod on M63 dev(10032.4.0/63.0.3239.7) in normal mode(quawks and lumpy).

Comment 11 by josa...@chromium.org, Oct 30 2017

Owner: abod...@chromium.org
Are you able to repro in dev mode? (with 10032.4.0/63.0.3239.7)

Comment 12 by abod...@chromium.org, Oct 30 2017

Owner: ----
even dev mode also not reproduced on quawks with 10032.4.0/63.0.3239.7.

Comment 13 by josa...@chromium.org, Oct 31 2017

Cc: -abodenha@chromium.org
Owner: abodenha@chromium.org
Albert, anyone who can help investigate this one?

Here is the diff on these builds: https://chromium.googlesource.com/chromium/src/+log/63.0.3239.7..63.0.3239.20?n=10000

Comment 14 by sdantul...@chromium.org, Oct 31 2017 

Issue is NOT Reproducible on AU from M62 beta to M63-DEV-CHROMEOS-7 (10032.21.0, 63.0.3239.26)

Comment 15 by josa...@chromium.org, Oct 31 2017

Status: WontFix (was: Assigned)
ok, closing as not repro
►

Sign in to add a comment