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

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


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

perf-go-phone-1024

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

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

Hi gab@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 : Gabriel Charette
  Commit : c9ba7a990ab0b915bf85cc17f5a9a5474cb92da7
  Date   : Thu May 10 21:10:59 2018
  Subject: [base] Add default arguments for WaitableEvent construction.

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background_social/background_social_facebook
  Change       : 2.64% | 84129556.0 -> 86350100.0

Revision                                       Result                   N
android-chrome@4426288b2b                      84129556 +- 860737       6      good
android-chrome@4426288b2b,chromium@557672      86220905 +- 438967       6      bad       <--
android-chrome@4426288b2b,chromium@557673      85400340 +- 472784       6      bad
android-chrome@4426288b2b,chromium@557675      85903977 +- 501416       6      bad
android-chrome@4426288b2b,chromium@557678      86002452 +- 605493       6      bad
android-chrome@4426288b2b,chromium@557684      85967465 +- 482141       6      bad
android-chrome@4426288b2b,chromium@557696      86651839 +- 231778       6      bad
android-chrome@4426288b2b,chromium@557721      86503017 +- 771510       6      bad
android-chrome@4426288b2b,chromium@557770      86826431 +- 437275       6      bad
android-chrome@4426288b2b,chromium@557868      87189268 +- 510650       6      bad
android-chrome@4426288b2b,chromium@558065      87548009 +- 700741       6      bad
android-chrome@dda312c828                      86350100 +- 1021755      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=background.social.facebook 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/8945704917451699584


For feedback, file a bug with component Speed>Bisection

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

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 81a3b828c376c285abf615d0573024b44cb46463
  bad_revision : 2ecdfaf5439c6e2e4ac60442e8d7df118701b446

If failures persist 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_os:system_memory:native_heap:proportional_resident_size_avg/load_media/load_media_google_images
  Change       : 0.94% | 28109949.7143 -> 27845245.7143

Revision                                       Result                   N
android-chrome@4426288b2b                      28109950 +- 282385       21      good
android-chrome@4426288b2b,chromium@557770      28185360 +- 313143       14      good
android-chrome@4426288b2b,chromium@557819      27974709 +- 291565       14      bad
android-chrome@4426288b2b,chromium@557868      27829520 +- 126694       14      bad
android-chrome@4426288b2b,chromium@558065      27839833 +- 97410.1      14      bad
android-chrome@dda312c828                      27845246 +- 165275       14      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.media.google.images 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/8945544306270304416


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist 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_os:system_memory:proportional_resident_size_avg/load_games/load_games_spychase
  Change       : 2.63% | 101640464.0 -> 104314640.0

Revision                                       Result                   N
android-chrome@4426288b2b                      101640464 +- 306188      6      good
android-chrome@4426288b2b,chromium@557678      104104379 +- 507872      6      bad
android-chrome@4426288b2b,chromium@557684      103953168 +- 709592      6      bad
android-chrome@4426288b2b,chromium@557696      103746149 +- 505639      6      bad
android-chrome@4426288b2b,chromium@557721      104218725 +- 345305      6      bad
android-chrome@4426288b2b,chromium@557770      104535995 +- 264695      6      bad
android-chrome@4426288b2b,chromium@557868      104352357 +- 316569      6      bad
android-chrome@4426288b2b,chromium@558065      104133904 +- 303207      6      bad
android-chrome@dda312c828                      104314640 +- 935422      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.games.spychase 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/8945544313125360432


For feedback, file a bug with component Speed>Bisection

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

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

Seriously doubt my CL is at fault and bisect is failing now so... tried relaunching bisect but setting back to Untriaged while it's running.

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_media/load_media_google_images
  Change       : 0.67% | 28074646.0952 -> 27886230.0952

Revision                       Result                  N
android-chrome@4426288b2b      28074646 +- 329192      21      good
android-chrome@dda312c828      27886230 +- 158458      21      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.media.google.images 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/8945280038118866176


For feedback, file a bug with component Speed>Bisection

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

Suspected Commit
  Author : Gabriel Charette
  Commit : c9ba7a990ab0b915bf85cc17f5a9a5474cb92da7
  Date   : Thu May 10 21:10:59 2018
  Subject: [base] Add default arguments for WaitableEvent construction.

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/load_games/load_games_spychase
  Change       : 3.86% | 101600016.0 -> 105525861.333

Revision                                       Result                   N
android-chrome@4426288b2b                      101600016 +- 327110      6      good
android-chrome@4426288b2b,chromium@557672      103658597 +- 231411      6      bad       <--
android-chrome@4426288b2b,chromium@557673      104052155 +- 291102      6      bad
android-chrome@4426288b2b,chromium@557675      103862203 +- 465401      6      bad
android-chrome@4426288b2b,chromium@557678      104229819 +- 190485      6      bad
android-chrome@4426288b2b,chromium@557684      104256272 +- 562548      6      bad
android-chrome@4426288b2b,chromium@557696      104202341 +- 629030      6      bad
android-chrome@4426288b2b,chromium@557721      104618427 +- 676148      6      bad
android-chrome@4426288b2b,chromium@557770      104962491 +- 158604      6      bad
android-chrome@4426288b2b,chromium@557868      104102843 +- 400007      6      bad
android-chrome@4426288b2b,chromium@558065      104717072 +- 275613      6      bad
android-chrome@dda312c828                      105525861 +- 346204      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.games.spychase 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/8945280032567121328


For feedback, file a bug with component Speed>Bisection