Chrome on Android DCHECK in personal_data_manager.cc if account removed from device |
|||
Issue descriptionWorking with a local debug build of Chrome for Android on Android M (MMB30D): 1. Sign Android in to a single account (I haven't tried multiple accounts) 2. Start a debug build of Chrome and sign in to that account (test builds will need the appropriate permissions enabled). 3. Kill Chrome 4. Remove the account from the device 5. Start Chrome Expected result: Chrome starts with no signed in account Actual: Chrome crashes with [FATAL:personal_data_manager.cc(337)] Check failed: !email.empty(). Tombstone file attached. Note:- This is currently interfering with backup/restore testing (issue 607535), and the release version doesn't crash when this is wrong, so, as a short term fix, I will remove the DCHECK in my CL for issue 607535.
,
Dec 19 2016
--Chrome Identity automated triaging-- This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 21 2016
Looking at personal_data_manager.cc, it seems the empty email case is now handled correctly (cf https://cs.chromium.org/chromium/src/components/autofill/core/browser/personal_data_manager.cc?l=378). Marking as fixed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by aber...@chromium.org
, May 10 2016