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

Issue 622285 link

Starred by 2 users
Status: WontFix
Owner:
█ petrcermak@chromium.org
Last visit > 30 days ago
Closed: Jun 2016
Cc:
vmi...@chromium.org
u...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Gmail failure on Android%20Nexus6%20Perf%20(2) at 401219:401238

Project Member Reported by petrcermak@chromium.org, Jun 22 2016 
Revision range first seen: r401219:r401238
Link to failing build: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf%20%282%29/builds/2958

The following 4 steps failed in the above build:
  * memory.long_running_idle_gmail_background_tbmv2
  * memory.long_running_idle_gmail_background_tbmv2.reference
  * smoothness.top_25_smooth
  * smoothness.top_25_smooth.reference

At first, the failures seemed unrelated, but then I noticed that all of them were on https://mail.google.com/mail/. It might of course be a coincidence, but it doesn't seem likely (given that the SAME url started failing at the SAME time).

The failures in memory.long_running_idle_gmail_background_tbmv2[.reference] are due to a browser crash during a memory dump:

Traceback (most recent call last):
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 85, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 319, in RunStory
    self._current_page.Run(self)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/page/__init__.py", line 99, in Run
    self.RunPageInteractions(action_runner)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/tools/perf/page_sets/long_running_idle_google_cases.py", line 30, in RunPageInteractions
    _IdleAction(action_runner)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/tools/perf/page_sets/long_running_idle_google_cases.py", line 17, in _IdleAction
    action_runner.tab.browser.DumpMemory()
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py", line 296, in DumpMemory
    return self._browser_backend.DumpMemory(timeout)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/chrome_browser_backend.py", line 289, in DumpMemory
    return self.devtools_client.DumpMemory(timeout)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_client_backend.py", line 374, in DumpMemory
    return self._tracing_backend.DumpMemory(timeout)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/tracing_backend.py", line 200, in DumpMemory
    'request:\n' + traceback.format_exc())
TracingUnrecoverableException: Exception raised while sending a Tracing.requestMemoryDump request:
Traceback (most recent call last):
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/tracing_backend.py", line 191, in DumpMemory
    response = self._inspector_websocket.SyncRequest(request, timeout)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 110, in SyncRequest
    res = self._Receive(timeout)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 149, in _Receive
    data = self._socket.recv()
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 596, in recv
    opcode, data = self.recv_data()
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 606, in recv_data
    frame = self.recv_frame()
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 637, in recv_frame
    self._frame_header = self._recv_strict(2)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 746, in _recv_strict
    bytes = self._recv(shortage)
  File "/b/build/slave/Android_Nexus6_Perf__2_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 739, in _recv
    raise WebSocketConnectionClosedException()
WebSocketConnectionClosedException

The failures in smoothness.top_25_smooth[.reference] are due to a native crash:

pid: 11261, tid: 11327, name: Thread-712  >>> org.chromium.chrome <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
[FATAL:jni_android.cc(236)] Please include Java exception stack in crash report
    r0 00000000  r1 00002c3f  r2 00000006  r3 00000000
    r4 99007db8  r5 00000006  r6 0000000b  r7 0000010c
    r8 b6e7edf4  r9 990078f4  sl 00000000  fp 00000000
    ip 00002c3f  sp 99007448  lr b6e283c5  pc b6e4b29c

Stack Trace:
  RELADDR   FUNCTION                                                          FILE:LINE
  0003a29c  tgkill+12                                                         /system/lib/libc.so
  000173c1  pthread_kill+52                                                   /system/lib/libc.so
  00017fd3  raise+10                                                          /system/lib/libc.so
  00014795  __libc_android_abort+36                                           /system/lib/libc.so
  00012f44  abort+4                                                           /system/lib/libc.so
  01398329  blink::SVGAnimatedOrder::checkValue(blink::SVGParsingError, int)  /mnt/data/b/build/slave/Android_Builder/build/src/third_party/WebKit/Source/core/svg/SVGFEConvolveMatrixElement.cpp:66

Java stderr from crashing pid (may identify underlying Java exception):
java.lang.AssertionError: At least one stream configuration for IMPLEMENTATION_DEFINED must exist
  at android.hardware.camera2.params.StreamConfigurationMap.<init>(StreamConfigurationMap.java:120)
  at android.hardware.camera2.impl.CameraMetadataNative.getStreamConfigurationMap(CameraMetadataNative.java:836)
  at android.hardware.camera2.impl.CameraMetadataNative.access$300(CameraMetadataNative.java:75)
  at android.hardware.camera2.impl.CameraMetadataNative$5.getValue(CameraMetadataNative.java:498)
  at android.hardware.camera2.impl.CameraMetadataNative.get(CameraMetadataNative.java:351)
  at android.hardware.camera2.impl.CameraMetadataNative.get(CameraMetadataNative.java:322)
  at android.hardware.camera2.CameraCharacteristics.get(CameraCharacteristics.java:170)
  at org.chromium.media.VideoCaptureCamera2.getDeviceSupportedFormats(VideoCaptureCamera2.java:426)
  at org.chromium.media.VideoCaptureFactory.getDeviceSupportedFormats(VideoCaptureFactory.java:137)

If the test is disabled, please downgrade to Pri-2.
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jun 22 2016 


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


===== TESTED REVISIONS =====
Revision         Exit Code  Std Dev  N  Good?
chromium@401218  0          N/A      2  good
chromium@401238  0          N/A      2  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 622285

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2245
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009151490307751360


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

| 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 3 by petrcermak@chromium.org, Jun 23 2016

Status: WontFix (was: Untriaged)
The issue has gone away as quickly as it appeared in the first place (see https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf%20%282%29), so I'm marking this as WontFix.
►

Sign in to add a comment