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

Issue 608448 link

Starred by 1 user
Status: WontFix
Owner:
█ pras...@chromium.org
Last visit 27 days ago
Closed: Jun 2016
Cc:
simonhatch@chromium.org
█ pras...@chromium.org
bokan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

smoothness.tough_pinch_zoom_cases failure on chromium.perf: Android Nexus 5X

Project Member Reported by simonhatch@chromium.org, May 2 2016

Comment 2 by bokan@chromium.org, May 4 2016 

Looks like the device is under memory pressure and things get killed? Not sure if that's a device problem or Chrome just started taking up too much memory in this case: 

	05-04 12:50:40.124   922 12617 I WindowState: WIN DEATH: Window{6b9610 u0 com.google.android.googlequicksearchbox/com.google.android.launcher.GEL}
	05-04 12:50:40.249   922   936 I ActivityManager: Start proc 27810:com.google.android.apps.photos/u0a65 for broadcast com.google.android.apps.photos/.scheduler.AlarmReceiver
	05-04 12:50:40.280   922  2861 W art     : Long monitor contention event with owner method=void com.android.server.am.BroadcastQueue.processNextBroadcast(boolean) from BroadcastQueue.java:639 waiters=0 for 142ms
	05-04 12:50:40.283   373   373 E lowmemorykiller: Error writing /proc/27791/oom_score_adj; errno=22
	05-04 12:50:40.289   922  3698 I ActivityManager: Process com.google.android.googlequicksearchbox (pid 3688) has died
	05-04 12:50:40.289   922  3698 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.reflection.ReflectionService in 19186ms
	05-04 12:50:40.290   373   373 E lowmemorykiller: Error writing /proc/27791/oom_score_adj; errno=22
	05-04 12:50:40.302   374   374 I ServiceManager: service 'AtCmdFwd' died
	05-04 12:50:40.308   922   933 I ActivityManager: Process com.qualcomm.telephony (pid 27791) has died
	05-04 12:50:40.308   922   933 W ActivityManager: Scheduling restart of crashed service com.qualcomm.atfwd/.AtFwdService in 19167ms
	05-04 12:50:40.465   520  5322 I ServiceManager: Waiting for service AtCmdFwd...
	05-04 12:50:40.585   922  3698 I ActivityManager: Process com.google.android.inputmethod.latin (pid 3507) has died
	05-04 12:50:40.586   922  3698 W ActivityManager: Scheduling restart of crashed service com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME in 28889ms
	05-04 12:50:40.663   922   934 I ActivityManager: Process com.google.android.gms.persistent (pid 3811) has died
	05-04 12:50:40.664   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.fused.service.FusedProviderService in 38811ms
	05-04 12:50:40.664   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.fused.FusedLocationService in 48811ms
	05-04 12:50:40.664   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.fitness.store.maintenance.StoreMaintenanceService in 58811ms
	05-04 12:50:40.664   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.GoogleLocationManagerService in 58811ms
	05-04 12:50:40.664   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.network.NetworkLocationService in 68811ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.deviceconnection.service.DeviceConnectionServiceBroker in 78811ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.PendingIntentCallbackService in 88811ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.common.stats.GmsCoreStatsService in 98810ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.backup.BackupTransportService in 108810ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.geocode.GeocodeService in 118810ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService in 128810ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.activity.HardwareArProviderService in 138810ms
	05-04 12:50:40.665   922   934 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.geofencer.service.GeofenceProviderService in 148810ms
	05-04 12:50:40.668   922  2902 D WifiService: Client connection lost with reason: 4
	05-04 12:50:40.755   922  2853 I sensors : activate
	05-04 12:50:40.783   922  2902 D WifiService: Client connection lost with reason: 4
	05-04 12:50:40.788   922  3070 I ActivityManager: Process com.google.process.gapps (pid 3757) has died
	05-04 12:50:40.788   922  3070 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.tapandpay.hce.service.TpHceService in 158687ms
	05-04 12:50:40.788   922  3070 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.gcm.GcmService in 168687ms
	05-04 12:50:40.832   922  2715 I hubconnection: sensorhub said: 'activate 12 enable:0'
	05-04 12:50:40.856   922  3329 I ActivityManager: Start proc 27827:com.google.process.gapps/u0a13 for service com.google.android.gms/.clearcut.service.ClearcutLoggerService
	05-04 12:50:40.953   922  3080 I ActivityManager: Process com.google.android.googlequicksearchbox:interactor (pid 3491) has died
	05-04 12:50:40.954   922  3080 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService in 178522ms
	05-04 12:50:40.954   922  5607 D GpsStatusListenerHelper: Remote Listener died: android.location.IGpsStatusListener$Stub$Proxy@c902c8
	05-04 12:50:41.046   922 27796 I ActivityManager: Low on memory:
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N    23399 kB: surfaceflinger (17280 kB memtrack) (pid 375) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N    21075 kB: zygote (pid 512) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     8777 kB: com.qualcomm.telephony (pid 27791) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     7219 kB: mediaserver (pid 690) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     3425 kB: zygote64 (pid 511) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     2926 kB: logd (pid 337) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     2181 kB: netmgrd (pid 507) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     1849 kB: rild (pid 497) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     1844 kB: ATFWD-daemon (pid 520) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     1244 kB: sdcard (pid 3005) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     1010 kB: mm-qcamera-daemon (pid 519) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N      926 kB: device_forwarder (pid 27738) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N      786 kB: adbd (pid 27428) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N      589 kB: /init (pid 1) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N      574 kB: thermal-engine (pid 508) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N      548 kB: perfprofd (pid 515) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N      524 kB: media.log (pid 499) native
	05-04 12:50:41.046   922 27796 I ActivityManager:   ntv   N     7144 kB: (Other native)
	05-04 12:50:41.047   922 27796 I ActivityManager:   sys   P    45988 kB: system (pid 922) fixed
	05-04 12:50:41.047   922 27796 I ActivityManager:   pers  P    82110 kB: com.android.systemui (15868 kB memtrack) (pid 3062) fixed
	05-04 12:50:41.047   922 27796 I ActivityManager:   pers  P    12191 kB: com.android.phone (pid 3653) fixed
	05-04 12:50:41.047   922 27796 I ActivityManager:   pers  P     9689 kB: com.android.nfc (pid 3598) fixed
	05-04 12:50:41.047   922 27796 I ActivityManager:   pers  P     4532 kB: com.quicinc.cne.CNEService (pid 3573) fixed
	05-04 12:50:41.047   922 27796 I ActivityManager:   pers  P     2901 kB: com.qualcomm.qti.rcsbootstraputil (pid 3620) fixed
	05-04 12:50:41.047   922 27796 I ActivityManager:   pers  P     2607 kB: com.qualcomm.qti.rcsimsbootstraputil (pid 3633) fixed
	05-04 12:50:41.047   922 27796 I ActivityManager:   fore  T  1041255 kB: org.chromium.chrome:sandboxed_process0 (pid 27647) service
	05-04 12:50:41.047   922 27796 I ActivityManager:                        org.chromium.chrome/org.chromium.content.app.SandboxedProcessService0<=Proc{27622:org.chromium.chrome/u0a82}
	05-04 12:50:41.047   922 27796 I ActivityManager:   fore  T    86465 kB: org.chromium.chrome (37540 kB memtrack) (pid 27622) top-activity
	05-04 12:50:41.047   922 27796 I ActivityManager:   fore  T    42046 kB: org.chromium.chrome:privileged_process0 (15584 kB memtrack) (pid 27680) service
	05-04 12:50:41.047   922 27796 I ActivityManager:                        org.chromium.chrome/org.chromium.content.app.PrivilegedProcessService0<=Proc{27622:org.chromium.chrome/u0a82}
	05-04 12:50:41.047   922 27796 I ActivityManager:   vis   T    24152 kB: com.google.android.googlequicksearchbox:search (pid 3855) service
	05-04 12:50:41.047   922 27796 I ActivityManager:                        com.google.android.googlequicksearchbox/com.google.android.ssb.service.SsbService<=Proc{27622:org.chromium.chrome/u0a82}
	05-04 12:50:41.047   922 27796 I ActivityManager:   vis   SB   18035 kB: com.google.android.gms.persistent (pid 3811) service
	05-04 12:50:41.047   922 27796 I ActivityManager:                        com.google.android.gms/com.google.android.location.geofencer.service.GeofenceProviderService<=Proc{922:system/1000}
	05-04 12:50:41.047   922 27796 I ActivityManager:   vis   IF   17130 kB: com.google.process.gapps (pid 3757) service
	05-04 12:50:41.047   922 27796 I ActivityManager:                        com.google.android.gms/.tapandpay.hce.service.TpHceService<=Proc{3598:com.android.nfc/1027}
	05-04 12:50:41.047   922 27796 I ActivityManager:   vis   SB    4120 kB: com.google.android.googlequicksearchbox:interactor (pid 3491) service
	05-04 12:50:41.047   922 27796 I ActivityManager:                        com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService<=Proc{922:system/1000}
	05-04 12:50:41.047   922 27796 I ActivityManager:   prcp  IB   11584 kB: com.google.android.inputmethod.latin (pid 3507) service
	05-04 12:50:41.047   922 27796 I ActivityManager:                        com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME<=Proc{922:system/1000}
	05-04 12:50:41.047   922 27796 I ActivityManager:   svc   S    13312 kB: com.google.android.googlequicksearchbox (13312 kB memtrack) (pid 3688) started-services
	05-04 12:50:41.047   922 27796 I ActivityManager:            1504157 kB: TOTAL (99584 kB memtrack)
	05-04 12:50:41.047   922 27796 I ActivityManager:   MemInfo: 76708 kB slab, 5432 kB shmem, 33576 kB vm alloc, 15164 kB page tables 15232 kB kernel stack
	05-04 12:50:41.047   922 27796 I ActivityManager:            224 kB buffers, 81484 kB cached, 64344 kB mapped, 212748 kB free
	05-04 12:50:41.047   922 27796 I ActivityManager:   ZRAM: 26680 kB RAM, 520908 kB swap total, 410508 kB swap free
	05-04 12:50:41.047   922 27796 I ActivityManager:   Free RAM: 230112 kB
	05-04 12:50:41.047   922 27796 I ActivityManager:   Used RAM: 1650269 kB
	05-04 12:50:41.047   922 27796 I ActivityManager:   Lost RAM: -23029 kB
	05-04 12:50:41.051   922   922 W InputMethodManagerService: Session failed to close due to remote exception
	05-04 12:50:41.051   922   922 W InputMethodManagerService: android.os.DeadObjectException
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at android.os.BinderProxy.transactNative(Native Method)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at android.os.BinderProxy.transact(Binder.java:503)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.internal.view.IInputMethodSession$Stub$Proxy.finishSession(IInputMethodSession.java:305)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.finishSessionLocked(InputMethodManagerService.java:1580)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.clearClientSessionLocked(InputMethodManagerService.java:1571)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.clearCurMethodLocked(InputMethodManagerService.java:1597)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.onServiceDisconnected(InputMethodManagerService.java:1616)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at android.app.LoadedApk$ServiceDispatcher.doDeath(LoadedApk.java:1228)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1242)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at android.os.Handler.handleCallback(Handler.java:739)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at android.os.Handler.dispatchMessage(Handler.java:95)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at android.os.Looper.loop(Looper.java:148)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.server.SystemServer.run(SystemServer.java:283)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.server.SystemServer.main(SystemServer.java:168)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at java.lang.reflect.Method.invoke(Native Method)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
	05-04 12:50:41.051   922   922 W InputMethodManagerService: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: Session failed to close due to remote exception
	05-04 12:50:41.093   922   922 W InputMethodManagerService: android.os.DeadObjectException
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at android.os.BinderProxy.transactNative(Native Method)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at android.os.BinderProxy.transact(Binder.java:503)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.internal.view.IInputMethodSession$Stub$Proxy.finishSession(IInputMethodSession.java:305)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.finishSessionLocked(InputMethodManagerService.java:1580)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.clearClientSessionLocked(InputMethodManagerService.java:1571)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.clearCurMethodLocked(InputMethodManagerService.java:1597)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.server.InputMethodManagerService.onServiceDisconnected(InputMethodManagerService.java:1616)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at android.app.LoadedApk$ServiceDispatcher.doDeath(LoadedApk.java:1228)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1242)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at android.os.Handler.handleCallback(Handler.java:739)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at android.os.Handler.dispatchMessage(Handler.java:95)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at android.os.Looper.loop(Looper.java:148)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.server.SystemServer.run(SystemServer.java:283)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.server.SystemServer.main(SystemServer.java:168)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at java.lang.reflect.Method.invoke(Native Method)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
	05-04 12:50:41.093   922   922 W InputMethodManagerService: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
	05-04 12:50:41.114   922  3656 W art     : Long monitor contention event with owner method=boolean android.os.BinderProxy.transactNative(int, android.os.Parcel, android.os.Parcel, int) from Binder.java:4294967294 waiters=0 for 590ms
	05-04 12:50:41.156   922   922 V BackupManagerService: Disconnected from transport ComponentInfo{com.google.android.gms/com.google.android.gms.backup.BackupTransportService}
	05-04 12:50:41.157   922   922 V BackupManagerService: Registering transport com.google.android.gms/.backup.BackupTransportService::null = null
	05-04 12:50:41.249   922  3713 W libprocessgroup: failed to open /acct/uid_10082/pid_27647/cgroup.procs: No such file or directory
	05-04 12:50:41.249   922  3713 I ActivityManager: Process org.chromium.chrome:sandboxed_process0 (pid 27647) has died
	05-04 12:50:41.250   922  3713 W ActivityManager: Scheduling restart of crashed service org.chromium.chrome/org.chromium.content.app.SandboxedProcessService0 in 158226ms
	05-04 12:50:41.466   520  5322 I ServiceManager: Waiting for service AtCmdFwd...
	05-04 12:50:41.466 27622 27622 W cr_ChildProcessConnect: onServiceDisconnected (crash or killed by oom): pid=27647
	05-04 12:50:41.792 27622 27622 I cr_TabWebContentsObs: renderProcessGone() for tab id: 0, oom protected: true, already needs reload: false
	05-04 12:50:42.052 27622 27622 I Choreographer: Skipped 30 frames!  The application may be doing too much work on its main thread.
	05-04 12:50:42.057 27827 27827 W System  : ClassLoader referenced unknown path: /system/priv-app/PrebuiltGmsCore/lib/arm64
	********************************************************************************

Comment 3 by bokan@chromium.org, May 5 2016

Cc: -bokan@chromium.org simonhatch@chromium.org
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)
Simon, could you kick off another bisect? Looks like I don't have permission since I'm no longer a perf sheriff

Comment 5 by pras...@chromium.org, May 11 2016 

This benchmark is still failing on 5X android bot. Last bisect failed, re-kicked another one
https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/172

Uploaded a patch to disable this test.

Comment 6 by bokan@chromium.org, May 11 2016

Cc: bokan@chromium.org
Owner: pras...@chromium.org
I'm not really sure what's going on here. In the first failing build (https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%283%29/builds/191) Simon posted in the original report, we still got results in the .json file so I can't really tell why the bot turned red. When I synced to the commit before the blamelist (i.e.  the previous build which was green on the waterfall: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%283%29/builds/190) and tried this benchmark locally, all but one tests pass, I get a crash on the calendar.google page. Same within the bad build's blamelist. Both the good and bad builds above seem to have results for calendar.google. Perhaps this is an infra issue?

The calendar.google crashes I see locally start at blink::PaintLayerScrollableArea::invalidateAllStickyConstraints so probably related to  issue 600377  and  issue 599505 , though both are fixed.

I'm OOO for the next 2 weeks so I won't be able to investigate any more. Prasad, could you find a better owner for this? Thanks.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, May 11 2016 


===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean   Std Dev  N  Good?
chromium@384291  55.0   0.0      5  good
chromium@384331  55.25  0.5      4  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 608448

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_pinch_zoom_cases
Test Metric: avg_surface_fps/avg_surface_fps
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/172
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9012933353407882720


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5786352788963328

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Comment 8 by sullivan@chromium.org, May 13 2016

Cc: pras...@chromium.org
 Issue 611481  has been merged into this issue.

Comment 9 by zh...@chromium.org, Jun 1 2016

Status: WontFix (was: Assigned)
Bot is now green and the benchmark is also enabled on Nexus 5X. The failure is somehow fixed. Closing this bug.
►

Sign in to add a comment