Debug Chrome for Android build crashes on navigation |
|||||
Issue descriptionChrome ToT crashes in debug build. Pixel, Android 7.1.2 Chrome built at 77cf3bbc98957d0f19da8b01afc47028c401cf79 gn args out/Debug: is_component_build = true run_findbugs=true enable_nacl = false use_goma = true is_debug = true target_os = "android" is_clang = true disable_incremental_isolated_processes=true media_use_ffmpeg = true media_use_libvpx = true proprietary_codecs = true ffmpeg_branding = "Chrome" enable_concurrent_apk_finalization = true What steps will reproduce the problem? 1. Open Chrome 2. Navigate to any page 3. Observe almost immediate crash. The stack trace from logcat: 07-12 17:36:37.128 773 13044 W Auth : [GetToken] GetToken failed with status code: INVALID_SCOPE 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: Failed to perform auth task 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: org.chromium.components.signin.AuthException: com.google.android.gms.auth.GoogleAuthException: INVALID_SCOPE 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at org.chromium.components.signin.SystemAccountManagerDelegate.getAuthToken(SystemAccountManagerDelegate.java:106) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:371) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:368) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:496) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:492) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at android.os.AsyncTask$2.call(AsyncTask.java:333) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at java.util.concurrent.FutureTask.run(FutureTask.java:266) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at java.lang.Thread.run(Thread.java:764) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: Caused by: com.google.android.gms.auth.GoogleAuthException: INVALID_SCOPE 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.zze$1.zzat(Unknown Source:126) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.zze$1.zzau(Unknown Source:0) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.zze.zza(Unknown Source:22) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.zze.zzc(Unknown Source:71) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.GoogleAuthUtil.zzc(Unknown Source:0) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.GoogleAuthUtil.zzb(Unknown Source:7) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.GoogleAuthUtil.zza(Unknown Source:14) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at com.google.android.gms.auth.GoogleAuthUtil.getTokenWithNotification(Unknown Source:0) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: at org.chromium.components.signin.SystemAccountManagerDelegate.getAuthToken(SystemAccountManagerDelegate.java:100) 07-12 17:36:37.134 17535 17568 W cr_Sync_Signin: ... 9 more
,
Jul 13 2017
I agree with Bernhard that this warning wouldn't cause a crash. I've seen this warning in unsigned builds of Chrome. In my case it was resolved by tapping notification and granting permission to access account info. This is probably not a P1 (official builds are signed, so it should affect developers only). Also, GoogleAuthException is not a UserRecoverableAuthException, so I'm not sure what can be done in this case. I'll build an unsigned Chrome later and check what's going on.
,
Jul 13 2017
I've copy pasted the whole logcat output and attached it here. The issue occurred after I installed the fresh unmodified debug build upon the (older & locally modified) release one. Once I uninstalled org.chromium.chrome and installed the same debug build again, the issue went away.
,
Jul 13 2017
From your logcat it looks like INVALID_SCOPE exception is not connected to the crash which is caused by strict mode violation. FATAL EXCEPTION: main Process: org.chromium.chrome, PID: 23276 android.os.StrictMode$StrictModeViolation: policy=18153503 violation=2 at android.os.StrictMode.executeDeathPenalty(StrictMode.java:1684) at android.os.StrictMode.-wrap3(Unknown Source:0) at android.os.StrictMode$AndroidBlockGuardPolicy.handleViolation(StrictMode.java:1677) at android.os.StrictMode$AndroidBlockGuardPolicy$1.run(StrictMode.java:1555) at android.os.Handler.handleCallback(Handler.java:789) at android.os.Handler.dispatchMessage(Handler.java:98) at android.os.Looper.loop(Looper.java:164) at android.app.ActivityThread.main(ActivityThread.java:6541) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
,
Jul 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/03613afa1f9182d58e9c27e65aee1c34465e24d4 commit 03613afa1f9182d58e9c27e65aee1c34465e24d4 Author: Boris Sazonov <bsazonov@chromium.org> Date: Tue Jul 18 09:47:55 2017 [Android] Revise AuthException This CL makes several changes to AuthException and its users: 1. Add second constructor that accepts message that can be used to report info about context that caused auth failure. 2. Use newly-added constructor to report authTokenScope that caused GoogleAuthException. 3. Add AuthException.TRANSIENT and AuthException.NONTRANSIENT constants to use in AuthException constructors. Bug: 741883 Change-Id: I6448ef2e4ecc66a885a0d3dc21f8665f678689ca Reviewed-on: https://chromium-review.googlesource.com/574541 Reviewed-by: Mihai Sardarescu <msarda@chromium.org> Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/master@{#487428} [modify] https://crrev.com/03613afa1f9182d58e9c27e65aee1c34465e24d4/components/signin/core/browser/android/java/src/org/chromium/components/signin/AuthException.java [modify] https://crrev.com/03613afa1f9182d58e9c27e65aee1c34465e24d4/components/signin/core/browser/android/java/src/org/chromium/components/signin/SystemAccountManagerDelegate.java
,
Jul 19 2017
I've added authTokenScope to the exception message to understand what context causes GoogleAuthException to happen. However, I still think that this exception has nothing to do with crash. Anton, do you still encounter this?
,
Aug 18 2017
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. 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
,
Aug 18 2017
I've added the logs and there's nothing else that can be done now about the crash Anton experience, so I'm closing this as WontFix. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bauerb@chromium.org
, Jul 13 2017Labels: -Pri-3 Pri-1
Owner: ----