Chrome ANR -- BackgroundTaskJobService
Reported by
liguozh...@xiaomi.corp-partner.google.com,
Jun 6 2018
|
|||||||||||
Issue descriptionSteps to reproduce the problem: NO What is the expected behavior? No ANR at all What went wrong? at java.lang.Object.wait!(Native method) - waiting on <0x03a727e5> (a java.lang.Object) at java.lang.Thread.parkFor$(Thread.java:2160) - locked <0x03a727e5> (a java.lang.Object) at sun.misc.Unsafe.park(Unsafe.java:325) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:161) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:840) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:203) at org.chromium.components.signin.AccountManagerFacade.getGoogleAccounts(AccountManagerFacade.java:37) at org.chromium.components.signin.AccountManagerFacade.tryGetGoogleAccounts(AccountManagerFacade.java:47) at org.chromium.components.signin.AccountManagerFacade.getAccountFromName(AccountManagerFacade.java:61) at org.chromium.chrome.browser.signin.OAuth2TokenService.hasOAuth2RefreshToken(OAuth2TokenService.java:39) at org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native method) at org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:9) at android.os.Handler.dispatchMessage(Handler.java:102) WebStore page: Did this work before? N/A Chrome version: 67.0.3396.68 Channel: stable OS Version: 6 & 7 Flash Version:
,
Jun 11 2018
I'll take a look at this.
,
Jun 25 2018
hello, several days passed, is there any update on this issue?
,
Jul 2
Dear chrome friend, do you have any updates on this issue?
,
Jul 2
Sorry for the delay. How often does the issue occur? Do you have any specific reproduction steps? The root cause: some Chrome APIs are designed in a way that they request account list synchronously. Sometimes Google Play services are slow to return the account list (especially after an update). If it takes more than 5 seconds - ANR will be shown. I have an idea how this can be mitigated, but it's a rather large change, so it won't be in M69, sorry.
,
Jul 3
Before answering your questions, I’d introduce our quality system, so you will understand how we works. The MIUI Quality System(MQS), is a platform to monitoring errors like crashes, ANRs, OOMs, etc. Once our user faces any kind of problem, a background service get the necessary data(log snapshot and device infos, etc.) and report to the MQS platform with user’s permission automatically and anonymously. While the platform found a certain issue has influenced a certain number of users, it create a Jira Issue automatically, and assign to me or someone else. Thus, some information can not be provided, like reproduce steps, because the problem occurred during user’s daily use, not by labs or testing team. Moreover, we can not recall a user to provide more information like screenshot, because all the process is automatically and anonymously. For other information, I’d send you a package of logs in attach. So far, it has influenced over thousand users
,
Jul 3
Ref. jira.n.xiaomi.com/browse/MIUIGLOBAL-10876 internal link as associated mark.
,
Nov 7
Quick update - I've landed several changes to fix these ANRs: https://crrev.com/c/1231935, https://crrev.com/c/1234233, https://crrev.com/c/1238559. These CLs should roll out in M-71. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by pnangunoori@chromium.org
, Jun 6 2018Labels: Needs-triage-Mobile Triaged-Mobile