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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxpW_lgsM


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

android-nexus5

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile_classic
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_social


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 v8.browsing_mobile_classic

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8977449469920261536

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5221483493720064


| 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 Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile_classic
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_social


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 v8.browsing_mobile_classic

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8977355406634931008

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5221483493720064


| 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 Speed>Bisection.  Thank you!

The browse_social regressions are caused by benchmark change (adding infinite scroll stories).

Other graphs have recovered.

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

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

Hi sebsg@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 : sebsg
  Commit : f8272a2043eeddf86177a2c643215d5060066122
  Date   : Fri May 26 14:32:58 2017
  Subject: [Payments] Move the logging for checkout flow to native.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/browse_news/browse_news_washingtonpost
  Change       : 0.35% | 64615928.3333 -> 64839006.0

Revision             Result                   N
chromium@475000      64615928 +- 59147.0      6      good
chromium@475001      64702659 +- 34368.1      6      bad       <--
chromium@475002      64687022 +- 21698.1      6      bad
chromium@475004      64694468 +- 71582.8      6      bad
chromium@475008      64699839 +- 59543.7      6      bad
chromium@475016      64780468 +- 143828       6      bad
chromium@475032      64700146 +- 96954.2      6      bad
chromium@475063      64729679 +- 169297       6      bad
chromium@475125      64724691 +- 227830       9      bad
chromium@475250      64684321 +- 68882.9      6      bad
chromium@475500      64703504 +- 55395.3      6      bad
chromium@476000      64697342 +- 246251       9      bad
chromium@477000      64839006 +- 160102       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-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/8972188343577571840


For feedback, file a bug with component Speed>Bisection