Android 4.1.2: Chrome failed during startup with an unexpected error
Reported by
joshnies...@gmail.com,
Mar 13 2016
|
|||||||||
Issue descriptionDevice name: HP 7 1800 tablet. From "Settings > About Chrome" Application version: 49.0.2623.95 or current BETA/DEV build. Platform version: 7834.60.0. OS: Android Jelly Bean 4.1.2. Steps to reproduce: (1) Attempt to open Chrome (2) Error pop-up: "Chrome failed during startup with an unexpected error". Expected result: Chrome should open normally, as it did with previous versions (48 and earlier). Actual result: After updating from 48.x to 49.0.2623.95, opening Google Chrome now gives error message and will not start. Also affects BETA, and DEV builds. Restarting device, reinstalling, and clearing cache does not work. Rolling back Chrome to factory version (4.9.385. Yes, OLD!) resolves issue.
,
Mar 14 2016
Can you please provide a bugreport and/or grab a chrome trace,if this happens again? For a bugreport, Android Settings > About Phone > Tap Build number 10 times, go back one screen, Developer options should be right above About phone. Check the USB debugging>and Take the bug report Chrome Trace : https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs#TOC-Capture-a-trace-from-Chrome-on-Android-with-DevTools-
,
Mar 15 2016
I'm from Chrome support, and am reporting this issue on behalf of a user. The user starts the bug report, but there is no way to stop and save it. No notification. Chrome Trace is to advanced to tackle from afar. Issue isn't intermittent. User is using Firefox for now.
,
Mar 15 2016
Thank you for providing more feedback. Assigning to requester "ppolisetty@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 17 2016
Hello Can you please let us know if this issue is still reproducible on the latest Chrome available on the play store? Thanks. We could not reproduce this issue on any tablet devices.
,
Nov 18 2016
Unable to reproduce issue on my end (Android 6.0), but devices still running Android Jelly Bean 4.1.2 are hard to find.
,
Nov 25 2016
Thank you for providing more feedback. Adding requester "ppolisetty@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Apr 26 2017
,
Nov 22 2017
Tested the issue with Chrome Stable# 62.0.3202.84 on Android 4.4.4 on Sony Xperia C902 and could not reproduce the issue. @joshniesler7 -- Could you please upgrade your Chrome to latest Stable and let us know the updated behavior. Thanks in Advance.
,
Jan 29 2018
Haven't seen any update on the bug in a while, hence closing. Please file a new issue if the issue is still happening. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by joshnies...@gmail.com
, Mar 13 201619.8 KB
19.8 KB View Download