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

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


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

perf-go-phone-1024

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

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

Hi chrishtr@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 : Chris Harrelson
  Commit : 93f946c0a26a54ee1d257b3e0de4ec8b154d5aba
  Date   : Mon Jun 25 04:34:37 2018
  Subject: [Fast compositing] Force compositing requirements update on change of stacking order.

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/browse_social/browse_social_pinterest_infinite_scroll
  Change       : 0.94% | 85363204.4444 -> 86096502.2222

Revision                                       Result                  N
android-chrome@8a569d566b                      85363204 +- 390863      9       good
android-chrome@8a569d566b,chromium@569963      85461565 +- 270809      6       good
android-chrome@8a569d566b,chromium@569964      86157178 +- 354259      14      bad       <--
android-chrome@8a569d566b,chromium@569966      86316093 +- 394775      9       bad
android-chrome@43d9ba3f14                      86146280 +- 191542      6       bad
android-chrome@5d6edbd629                      85919610 +- 335589      14      bad
android-chrome@ef9854664b                      86096502 +- 255117      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.pinterest.infinite.scroll 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/8942614947392925792


For feedback, file a bug with component Speed>Bisection

This was a correctness fix. Offset by bigger changes earlier.