New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 758914 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 752510
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Google Chrome : ANR occured on Xperia devices for Xperia Messaging application

Reported by arun.ra...@sony.corp-partner.google.com, Aug 25 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Open Xperia messaging app.
2. Open any conversation thread.
3. After some time the app will crash.

What is the expected behavior?
ANR should not occur on Xperia Messaging application due to Google Chrome update when calling Linkify.ALL API.

What went wrong?
After updating Google Chrome to 60.0.3112.107, it causes continous ANR for Xperia Messaging application on Xperia devices.
Xperia Messaging application calls "Linkify.addLinks(SpannableString, Linkify.ALL)".
According to the ANR there is a call to 'runOnUiThreadBlocking' by Google Chrome.
https://chromium.googlesource.com/chromium/src/base/+/master/android/java/src/org/chromium/base/ThreadUtils.java#71
which posts the task on the UI thread and causes ANR.

Did this work before? Yes 59.0.3071.125

Chrome version: 60.0.3112.107  Channel: stable
OS Version: 
Flash Version: 

Xperia Messaging application calls "Linkify.addLinks(SpannableString, Linkify.ALL)".
After update to Google Chrome (60.0.3112.107), according to the ANR there is a call to 'runOnUiThreadBlocking' by Google Chrome.
https://chromium.googlesource.com/chromium/src/base/+/master/android/java/src/org/chromium/base/ThreadUtils.java#71
which posts the task on the UI thread and causes ANR.

  at java.lang.Object.wait!(Native method)
  - waiting to lock <0x0d93c648> (a java.lang.Object) held by thread 1
  at com.android.webview.chromium.WebViewChromiumFactoryProvider.ensureChromiumStartedLocked(WebViewChromiumFactoryProvider.java:155)
  at com.android.webview.chromium.WebViewChromiumFactoryProvider.getStatics(WebViewChromiumFactoryProvider.java:257)
  - locked <0x0d93c648> (a java.lang.Object)
  at android.webkit.WebView.findAddress(WebView.java:1727)
  at android.text.util.Linkify.gatherMapLinks(Linkify.java:551)

"main" prio=5 tid=1 Waiting
  | group="main" sCount=1 dsCount=0 obj=0x75660970 self=0x7f7c896a00
  | sysTid=1296 nice=-10 cgrp=default sched=0/0 handle=0x7f807d5a98
  | state=S schedstat=( 655498130 75207148 1120 ) utm=49 stm=16 core=5 HZ=100
  | stack=0x7ff5c28000-0x7ff5c2a000 stackSize=8MB
  | held mutexes=
  at java.lang.Object.wait!(Native method)
  - waiting on <0x08d0f8eb> (a java.lang.Object)
  at java.lang.Thread.parkFor$(Thread.java:2127)
  - locked <0x08d0f8eb> (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.FutureTask.awaitDone(FutureTask.java:421)
  at java.util.concurrent.FutureTask.get(FutureTask.java:163)
  at android.os.AsyncTask.get(AsyncTask.java:514)
  at org.chromium.content.browser.BrowserStartupController.prepareToStartBrowserProcess(BrowserStartupController.java:57)
  at org.chromium.content.browser.BrowserStartupController.startBrowserProcessesSync(BrowserStartupController.java:16)
  at org.chromium.android_webview.AwBrowserProcess$1.run(AwBrowserProcess.java:14)
  at org.chromium.base.ThreadUtils.runOnUiThreadBlocking(ThreadUtils.java:10)
  at com.android.webview.chromium.WebViewChromiumFactoryProvider.startChromiumLocked(WebViewChromiumFactoryProvider.java:219)
  at com.android.webview.chromium.WebViewChromiumFactoryProvider$1.run(WebViewChromiumFactoryProvider.java:5)
  - locked <0x0d93c648> (a java.lang.Object)
  at android.os.Handler.handleCallback(Handler.java:751)
  at android.os.Handler.dispatchMessage(Handler.java:95)
  at android.os.Looper.loop(Looper.java:245)
  at android.app.ActivityThread.main(ActivityThread.java:6274)
  at java.lang.reflect.Method.invoke!(Native method)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

Issue not reproducible with Google Chrome (Beta) and previous versions to 60.
 
crash-java-20170823-135610.zip
3.8 MB Download
This is a nasty issue that will affect a very large number of Sony devices when the user updates Chrome to version 60. Is there any chance that the update can be pulled and replaced with the beta version that does not exhibit this issue?
Labels: Needs-Triage-M60 Needs-Feedback
arun.rathi@ Thanks for the issue.

Can you please confirm if this issue is related to Google Chrome Desktop or related to Android, which will help us in further triaging of the issue?

Thanks...
This issue is related to Android.
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 28 2017

Cc: susanjuniab@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by boliu@chromium.org, Aug 28 2017

Components: Mobile>WebView
Mergedinto: 752510
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment