All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=846680

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=4ebca1926057b5c89d92d1315dc991ef8b5ffbe92bfca651af889fe82980e756


Bot(s) for this bug's original alert(s):

perf-go-phone-1024

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

=== Auto-CCing suspected CL author szager@chromium.org ===

Hi szager@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Stefan Zager
  Commit : ae1e5c2742a0e197cd200409c9e59f4e6e1f5e7a
  Date   : Fri May 04 18:15:03 2018
  Subject: Add profiling interface to chrome.gpuBenchmarking

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_tools/load_tools_docs
  Change       : 17.80% | 1311248.0 -> 1544714.0

Revision                                       Result                  N
android-chrome@70a5c38d16                      1311248 +- 2489.31      6      good
android-chrome@42402a1b3d                      1310230 +- 41.1631      6      good
android-chrome@42402a1b3d,chromium@556117      1310230 +- 41.1631      6      good
android-chrome@42402a1b3d,chromium@556120      1310222 +- 33.4425      6      good
android-chrome@42402a1b3d,chromium@556121      1544695 +- 104.021      6      bad       <--
android-chrome@42402a1b3d,chromium@556122      1544764 +- 24.7871      6      bad
android-chrome@42402a1b3d,chromium@556127      1544777 +- 50.4962      6      bad
android-chrome@42402a1b3d,chromium@556146      1544703 +- 127.365      6      bad
android-chrome@da329c4b5b                      1544714 +- 154.728      6      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.docs 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/8945556521744481872


For feedback, file a bug with component Speed>Bisection

There is a 0% chance that my commit caused this regression.

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_tools/load_tools_docs


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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.docs 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/8945198262794359168


For feedback, file a bug with component Speed>Bisection