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

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


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

android-one

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

=== Auto-CCing suspected CL author matthalp@google.com ===

Hi matthalp@google.com, 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 : Matthew Halpern
  Commit : cd7e31fb911a98c7dc021d543e9dea8c553cdb1f
  Date   : Wed Jul 19 20:50:43 2017
  Subject: Enable GRC

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_nytimes
  Change       : 0.46% | 15083548.9286 -> 15153059.1111

Revision             Result                  N
chromium@487900      15083549 +- 249875      14      good
chromium@487964      15046495 +- 396052      14      good
chromium@487966      15070877 +- 337465      14      good
chromium@487967      15049545 +- 288474      14      good
chromium@487968      15113568 +- 459136      14      bad       <--
chromium@487972      15156459 +- 231039      14      bad
chromium@487980      15134234 +- 387436      21      bad
chromium@487996      15166520 +- 132376      14      bad
chromium@488028      15153059 +- 194383      9       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=load.news.nytimes 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/8973189278212852448


For feedback, file a bug with component Speed>Bisection

I'm going to put the status to assigned, please assign back to me and put the status to untriaged if you don't think this has ended up on the right CL, thanks!

 Issue 747938  has been merged into this issue.

 Issue 749356  has been merged into this issue.

oysteine: any update here?

Closing since all these regressions are less than 1MiB and the bug is quite old at this point.