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

Issue 712590 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 709436



Sign in to add a comment

browse:chrome:newtab failing with Chrome crashes

Project Member Reported by perezju@chromium.org, Apr 18 2017

Issue description

This story has been consistently crashing since it started running on the bots:

- android-one
- android-nexus7v2
- android-nexus6
- android-nexus5

The logs show a TimeoutException from dev-tools but with no message:

  File "/b/c/b/Android_Nexus7v2_Perf__1_/src/third_party/catapult/telemetry/third_party/websocket-client/websocket/_socket.py", line 83, in recv
    raise WebSocketTimeoutException(message)
TimeoutException: 
********************************************************************************
(/b/c/b/Android_Nexus7v2_Perf__1_/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:477 _ConvertExceptionFromInspectorWebsocket) The app is probably crashed:

And a non-symbolized Chrome crash:

	I    1.535s Main  pid: 600, tid: 600, name: app_process  >>> app_process <<<
	I    1.535s Main  signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
	I    1.535s Main      r0 00000000  r1 00000258  r2 00000006  r3 00000000
	I    1.535s Main      r4 00000006  r5 00000002  r6 00000258  r7 0000010c
	I    1.535s Main      r8 00000004  r9 befe4b91  sl befe4b9d  fp befe4b85
	I    1.535s Main      ip 4026e438  sp befe4628  lr 40108fe5  pc 40117f90
	I    1.535s Main  
	I    1.535s Main  Stack Trace:
	I    1.535s Main    RELADDR   FUNCTION                                                      FILE:LINE
	I    1.535s Main    00021f90  tgkill+12                                                     /system/lib/libc.so
	I    1.535s Main    00012fe1  pthread_kill+48                                               /system/lib/libc.so
	I    1.535s Main    000131f5  raise+10                                                      /system/lib/libc.so
	I    1.535s Main    00011f2b  <unknown>                                                     /system/lib/libc.so
	I    1.535s Main    00021844  abort+4                                                       /system/lib/libc.so
	I    1.535s Main    00045cc7  dvmAbort+78                                                   /system/lib/libdvm.so
	I    1.535s Main    00001fab  jniRegisterNativeMethods+42                                   /system/lib/libnativehelper.so
	I    1.535s Main    0004cd25  <unknown>                                                     /system/lib/libandroid_runtime.so
	I    1.535s Main    0004d011  android::AndroidRuntime::startReg(_JNIEnv*)+24                /system/lib/libandroid_runtime.so
	I    1.535s Main    0004da61  android::AndroidRuntime::start(char const*, char const*)+184  /system/lib/libandroid_runtime.so
	I    1.535s Main    0000105b  <unknown>                                                     /system/bin/app_process
	I    1.535s Main    0000e34b  __libc_init+50                                                /system/lib/libc.so
	I    1.535s Main    00000d7c  <unknown>                                                     /system/bin/app_process

Full log:
https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus7v2_Perf__1_%2F5030%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_mobile%2F0%2Fstdout

Screenshot does not anything too interesting:
https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_203-2017-04-17_20-28-322176.png

I'll proceed disabling this story.
 
Project Member

Comment 2 by bugdroid1@chromium.org, Apr 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6a10d876438a19c51bf3d73d7f4484255718a5a2

commit 6a10d876438a19c51bf3d73d7f4484255718a5a2
Author: perezju <perezju@chromium.org>
Date: Tue Apr 18 11:39:19 2017

[tools/perf] Disable browse:chrome:newtab

Story is failing on android bots.

TBR=nednguyen@google.com,ssid@chromium.org
BUG= 712590 

Review-Url: https://codereview.chromium.org/2827623002
Cr-Commit-Position: refs/heads/master@{#465199}

[modify] https://crrev.com/6a10d876438a19c51bf3d73d7f4484255718a5a2/tools/perf/page_sets/system_health/searching_stories.py

Comment 3 by ssid@chromium.org, Apr 18 2017

Cc: mikec...@chromium.org rnep...@chromium.org jbudorick@chromium.org
+John, Randy, Mike Does anyone know why this failure happens?
Seems to crash outside chrome library.
Blocking: 709436

Comment 5 by ssid@chromium.org, Apr 24 2017

Okay I just realized that the stack trace might be not related to the benchmark failing. The tombstones contain some old android crashes that we symbolize in bots. But it could be related too.

The actual reason for the failure is the adb shell input commands not working. The screenshot shows that the newtab page is open, but the text input is not present on the url_bar. There are some related log messages:
	D/AndroidRuntime( 7114): Calling main entry com.android.commands.input.Input
	I/Input   ( 7114): injectKeyEvent: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_ENTER, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=9050285, downTime=9050285, deviceId=-1, source=0x101 }
	E/PowerHAL(  796): touch_boost: failed to send: Connection refused
	E/PowerHAL(  796): touch_boost: failed to send: Connection refused
	W/dalvikvm( 6935): VFY: unable to find class referenced in signature (Landroid/view/KeyboardShortcutGroup;)
	E/dalvikvm( 6935): Could not find class 'android.view.KeyboardShortcutInfo', referenced from method org.chromium.chrome.browser.KeyboardShortcuts.addShortcut
	W/dalvikvm( 6935): VFY: unable to resolve new-instance 2115 (Landroid/view/KeyboardShortcutInfo;) in Lorg/chromium/chrome/browser/KeyboardShortcuts;
	D/dalvikvm( 6935): VFY: replacing opcode 0x22 at 0x0000
	D/dalvikvm( 6935): DexOpt: unable to opt direct call 0x3293 at 0x06 in Lorg/chromium/chrome/browser/KeyboardShortcuts;.addShortcut
	I/Input   ( 7114): injectKeyEvent: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_ENTER, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=9050285, downTime=9050285, deviceId=-1, source=0x101 }
	E/PowerHAL(  796): touch_boost: failed to send: Connection refused
	E/PowerHAL(  796): touch_boost: failed to send: Connection refused

Comment 6 by ssid@chromium.org, Apr 24 2017

I don't see any logs related to the injected keyevents in case of the search texts.

The commands that are run are printed as:
(INFO) 2017-04-17 17:42:49,833 cmd_helper._ValidateAndLogCommand:161  [host]> /b/c/b/Android_Nexus5_Perf__2_/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 0d88db4443e4b0d5 shell '( input text '"'"'does google know everything'"'"' );echo %$?'
(INFO) 2017-04-17 17:42:50,765 cmd_helper._ValidateAndLogCommand:161  [host]> /b/c/b/Android_Nexus5_Perf__2_/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 0d88db4443e4b0d5 shell '( input keyevent 66 );echo %$?'


Running the test locally prints logs for each keyevent:
04-24 21:03:26.726 20416 20416 D AndroidRuntime: Calling main entry com.android.commands.input.Input
04-24 21:03:26.730 20416 20416 I Input   : injectKeyEvent: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_D, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=436074885, downTime=436074885, deviceId=-1, source=0x101 }
04-24 21:03:26.741 20416 20416 I Input   : injectKeyEvent: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_D, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=436074885, downTime=436074885, deviceId=-1, source=0x101 }
04-24 21:03:26.746 20416 20416 I Input   : injectKeyEvent: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_O, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=436074885, downTime=436074885, deviceId=-1, source=0x101 }
04-24 21:03:26.752 20416 20416 I Input   : injectKeyEvent: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_O, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=436074885, downTime=436074885, deviceId=-1, source=0x101 }
04-24 21:03:26.754 20416 20416 I Input   : injectKeyEvent: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_E, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=436074885, downTime=436074885, deviceId=-1, source=0x101 }
04-24 21:03:29.025 20416 20416 D AndroidRuntime: Shutting down VM



But the logcat on the bot only shows this:
	D/AndroidRuntime( 7101): Calling main entry com.android.commands.input.Input
	D/AndroidRuntime( 7101): Shutting down VM
Project Member

Comment 7 by bugdroid1@chromium.org, Apr 26 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6869120a3a97c50c14188109cd32987bf7f27bb7

commit 6869120a3a97c50c14188109cd32987bf7f27bb7
Author: catapult-deps-roller@chromium.org <catapult-deps-roller@chromium.org>
Date: Wed Apr 26 23:38:18 2017

Roll src/third_party/catapult/ abff3b492..685851048 (1 commit)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/abff3b4929c7..6858510487e6

$ git log abff3b492..685851048 --date=short --no-merges --format='%ad %ae %s'
2017-04-26 ssid Fix android_action_runner.InputSwipe and InputText

Created with:
  roll-dep src/third_party/catapult
BUG=708300, 712590 


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: Ic97851766db7f7a5b0d49cb2ee74b936220f1d34
Reviewed-on: https://chromium-review.googlesource.com/487731
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#467510}
[modify] https://crrev.com/6869120a3a97c50c14188109cd32987bf7f27bb7/DEPS

Project Member

Comment 8 by bugdroid1@chromium.org, Apr 27 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8a4c38833ae890a2b12fb416d4c9375a6de5c051

commit 8a4c38833ae890a2b12fb416d4c9375a6de5c051
Author: ssid <ssid@chromium.org>
Date: Thu Apr 27 04:29:37 2017

Revert of [tools/perf] Disable browse:chrome:newtab (patchset #1 id:1 of https://codereview.chromium.org/2827623002/ )

Reason for revert:
The issue with InputText was fixed in crrev.com/2822573002

Original issue's description:
> [tools/perf] Disable browse:chrome:newtab
>
> Story is failing on android bots.
>
> TBR=nednguyen@google.com,ssid@chromium.org
> BUG= 712590 
>
> Review-Url: https://codereview.chromium.org/2827623002
> Cr-Commit-Position: refs/heads/master@{#465199}
> Committed: https://chromium.googlesource.com/chromium/src/+/6a10d876438a19c51bf3d73d7f4484255718a5a2

TBR=nednguyen@google.com,perezju@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 712590 

Review-Url: https://codereview.chromium.org/2844883004
Cr-Commit-Position: refs/heads/master@{#467579}

[modify] https://crrev.com/8a4c38833ae890a2b12fb416d4c9375a6de5c051/tools/perf/page_sets/system_health/searching_stories.py

Comment 9 by ssid@chromium.org, May 2 2017

Status: Fixed (was: Assigned)

Sign in to add a comment