Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971732341652318560

=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_news/browse_news_washingtonpost

Revision             Exit Code      N
chromium@489862      0 +- N/A       20      good
chromium@490186      0 +- N/A       20      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.washingtonpost system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8971732341652318560


For feedback, file a bug with component Speed>Bisection

The logs says that tracing is failing on cnn. This story has high memory usage. I suspect that Android OOM killer might be killing the browser.

To confirm that I need the logcat output from the device, which I cannot find on the bot page.

martiniss@, nednguyen@, was logcat output logging removed from the bots? I remember that before I could inspect logcat.


Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 107, in _RunStoryAndProcessErrorIfNeeded
    test.Measure(state.platform, results)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py", line 285, in Measure
    trace_result = platform.tracing_controller.StopTracing()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/core/tracing_controller.py", line 47, in StopTracing
    return self._tracing_controller_backend.StopTracing()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 140, in StopTracing
    '\n'.join(raised_exception_messages))
TracingException: Exceptions raised when trying to stop tracing:
Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 128, in StopTracing
    agent.CollectAgentTraceData(builder)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py", line 250, in CollectAgentTraceData
    '\n'.join(raised_exception_messages))
ChromeTracingStoppedError: Exceptions raised when trying to collect Chrome devtool tracing:
Error when collecting Chrome tracing on devtools at port localabstract:chrome_devtools_remote:
Traceback (most recent call last):

The latest build shows a different failure:
https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F404%2F%2B%2Frecipes%2Fsteps%2Fv8.browsing_mobile_on_Android%2F0%2Fstdout

Exception: At most one instance of process org.chromium.chrome expected but found pids: defaultdict(<type 'list'>, {'org.chromium.chrome:sandboxed_process0': ['11866'], 'org.chromium.chrome': ['11834', '11929']})
Locals:
  pids : defaultdict(<type 'list'>, {'org.chromium.chrome:sandboxed_process0': ['11866'], 'org.chromium.chrome': ['11834', '11929']})

Still failing.