New issue
Advanced search Search tips

Issue 896740 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

[Internal] The chrome exception causes the phone to freeze screen

Project Member Reported by gkadiyala@google.com, Oct 18

Issue description

DESCRIPTION:
logcat\logcat\logcat_events.txt
10-13 12:28:08.921  1547  3001 I watchdog: Blocked in monitor com.android.server.am.ActivityManagerService on foreground thread (android.fg), Blocked in handler on main thread (main), Blocked in handler on ui thread (android.ui), Blocked in handler on display thread (android.display), Blocked in handler on ActivityManager (ActivityManager).
Dog timeout restart

BUILD FINGERPRINT:

PACKAGE NAME AFFECTED (e.g. com.google.android.dialer) : 
com.android.chrome              67.0.3396.87
STEPS TO REPRODUCE: (please be specific) 
1. Mobile phone performs monkey test
2. Found a frozen screen phenomenon, check the log found that "Binder: 1547_1C" and process 29895 (com.android.chrome) communication timed out
3.
...



 
Our internal analysis :
logcat\logcat\logcat_events.txt
10-13 12:28:08.921  1547  3001 I watchdog: Blocked in monitor com.android.server.am.ActivityManagerService on foreground thread (android.fg), Blocked in handler on main thread (main), Blocked in handler on ui thread (android.ui), Blocked in handler on display thread (android.display), Blocked in handler on ActivityManager (ActivityManager).Dog timeout restart

bc7819 _freeze screen/bugreport.txt
----- pid 1547 at 2018-10-16 03:02:49 -----
Cmd line: system_server
"main" prio=5 tid=1 Blocked
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x738ad9d0 self=0x72a68c2a00
  | sysTid=1547 nice=-2 cgrp=default sched=0/0 handle=0x732b54f9a8
  | state=S schedstat=( 1762109680546 757608927795 5512684 ) utm=111300 stm=64910 core=7 HZ=100
  | stack=0x7fdfdcf000-0x7fdfdd1000 stackSize=8MB
  | held mutexes=
  at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:21447)
  - waiting to lock <0x03cfdc77> (a com.android.server.am.ActivityManagerService) held by thread 94

The main thread is blocked, and the lock <0x03cfdc77> is held by the thread "Binder:1547_1C"

"Binder:1547_1C" prio=5 tid=94 Native
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x12ecc668 self=0x72738e7a00
  | sysTid=28709 nice=-2 cgrp=default sched=0/0 handle=0x72837144f0
  | state=S schedstat=( 1261677862646 384518729409 2631521 ) utm=91867 stm=34300 core=7 HZ=100
  | stack=0x728361a000-0x728361c000 stackSize=1005KB
  | held mutexes=
  kernel: (couldn't read /proc/self/task/28709/stack)
  native: #00 pc 000000000006a54c  /system/lib64/libc.so (__ioctl+4)
  native: #01 pc 00000000000244b8  /system/lib64/libc.so (ioctl+136)
  native: #02 pc 0000000000054a30  /system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+256)
  native: #03 pc 000000000005578c  /system/lib64/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+340)
  native: #04 pc 00000000000554d8  /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+224)
  native: #05 pc 000000000004c310  /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+72)
  native: #06 pc 000000000004c06c  /system/lib64/libbinder.so (android::BpBinder::getInterfaceDescriptor() const+136)
  native: #07 pc 000000000011f938  /system/lib64/libandroid_runtime.so (???)
  native: #08 pc 0000000000921474  /system/framework/arm64/boot-framework.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+196)
  at android.os.BinderProxy.transactNative(Native method)
  at android.os.BinderProxy.transact(Binder.java:764)
  at android.app.IServiceConnection$Stub$Proxy.connected(IServiceConnection.java:95)
  at com.android.server.am.ActiveServices.publishServiceLocked(ActiveServices.java:1565)
  at com.android.server.am.ActivityManagerService.publishService(ActivityManagerService.java:20058)
  - locked <0x03cfdc77> (a com.android.server.am.ActivityManagerService)
  at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:613)
  at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3546)
  at android.os.Binder.execTransact(Binder.java:697)
  
pending transaction 259522305: ffffffc039868e00 from 1547:28709 to 29895:0 code 5f4e5446 flags 10 pri 0:118 r1 node 259521570 size 0:0 data ffffff8010f01dc0

  "Binder: 1547_1C" and process 29895 (com.android.chrome) communication timed out

----- pid 29895 at 2018-10-16 03:02:55 -----
Cmd line: com.android.chrome
"Binder:29895_1" prio=5 tid=8 Waiting
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x12c80460 self=0xe040fc00
  | sysTid=29906 nice=0 cgrp=default sched=0/0 handle=0xcfa2f970
  | state=S schedstat=( 3520938 9480469 25 ) utm=0 stm=0 core=6 HZ=100
  | stack=0xcf935000-0xcf937000 stackSize=1006KB
  | held mutexes=
  at java.lang.Object.wait(Native method)
  - waiting on <0x0425a8ee> (a java.lang.Object)
  at java.lang.Thread.parkFor$(Thread.java:2137)
  - locked <0x0425a8ee> (a java.lang.Object)
  at sun.misc.Unsafe.park(Unsafe.java:358)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:190)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2059)
  at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
  at avR.a(PG:36)
  at avR.onDataSetChanged(PG:27)
  at android.widget.RemoteViewsService$RemoteViewsFactoryAdapter.onDataSetChanged(RemoteViewsService.java:142)
  - locked <0x0395a18f> (a android.widget.RemoteViewsService$RemoteViewsFactoryAdapter)
  at com.android.internal.widget.IRemoteViewsFactory$Stub.onTransact(IRemoteViewsFactory.java:49)
  at android.os.Binder.execTransact(Binder.java:697)

"Binder:29895_2" prio=5 tid=9 Waiting
  | group="main" sCount=1 dsCount=0 flags=1 obj=0x12c804e8 self=0xe0146c00
  | sysTid=29907 nice=0 cgrp=default sched=0/0 handle=0xcf932970
  | state=S schedstat=( 33188635 878071 87 ) utm=1 stm=2 core=6 HZ=100
  | stack=0xcf838000-0xcf83a000 stackSize=1006KB
  | held mutexes=
  at java.lang.Object.wait(Native method)
  - waiting on <0x01898c1c> (a java.lang.Object)
  at java.lang.Thread.parkFor$(Thread.java:2137)
  - locked <0x01898c1c> (a java.lang.Object)
  at sun.misc.Unsafe.park(Unsafe.java:358)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:190)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2059)
  at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
  at avR.a(PG:36)
  at avR.onDataSetChanged(PG:27)
  at android.widget.RemoteViewsService$RemoteViewsFactoryAdapter.onDataSetChanged(RemoteViewsService.java:142)
  - locked <0x09e96025> (a android.widget.RemoteViewsService$RemoteViewsFactoryAdapter)
  at com.android.internal.widget.IRemoteViewsFactory$Stub.onTransact(IRemoteViewsFactory.java:49)
  at android.os.Binder.execTransact(Binder.java:697)

"Binder:29895_3" prio=5 tid=18 Waiting
"Binder:29895_4" prio=5 tid=37 Waiting
"Binder:29895_5" prio=5 tid=39 Waiting
"Binder:29895_6" prio=5 tid=40 Waiting
"Binder:29895_7" prio=5 tid=42 Waiting
"Binder:29895_8" prio=5 tid=41 Waiting
"Binder:29895_9" prio=5 tid=44 Waiting
"Binder:29895_A" prio=5 tid=45 Waiting
"Binder:29895_B" prio=5 tid=43 Waiting
"Binder:29895_C" prio=5 tid=46 Waiting
"Binder:29895_D" prio=5 tid=47 Waiting
"Binder:29895_E" prio=5 tid=48 Waiting
"Binder:29895_F" prio=5 tid=50 Waiting
"Binder:29895_10" prio=5 tid=51 Waiting

I hope that Google can assist in the analysis from within the application.

Unable to attach the bug report from the partners issue, since it is too long .
Please check the partner issue: https://b.corp.google.com/issues/117913489 for bug report.


Thanks.
cc:android-bug triage@google.com
Labels: Needs-triage-Mobile Stability-Hang OS-Android
Chrome team, could you please update the bug?
Chrome team, could you please update the bug?

Sign in to add a comment