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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2oOzrwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2uHv8QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2v2EuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2q3b_AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguuicpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2rmQhQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2s6EqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2t_PtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2sybtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2sr7rQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmu_T4goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmu_T4ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2rvcrQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2pbbrwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2uzhowoM


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

android-nexus5X
android-nexus6
chromium-rel-mac11-pro
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

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

Hi rmcilroy@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 : Ross McIlroy
  Commit : de4a4095cf22bc3c9cfa13eb5f8be28eb7a5f031
  Date   : Thu May 18 10:41:48 2017
  Subject: [Heap] Disable code flushing in preparation to remove it.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.mobile_infinite_scroll-classic_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/pinterest
  Change       : 25.84% | 29265002.0 -> 36825719.3333

Revision                           Result                   N
chromium@472757                    29265002 +- 3036751      6      good
chromium@472813                    29666391 +- 4085691      6      good
chromium@472841                    27767683 +- 3753868      6      good
chromium@472855                    28274198 +- 3713075      6      good
chromium@472855,v8@5e9939214e      29141529 +- 4251826      6      good
chromium@472855,v8@de4a4095cf      37964023 +- 3666898      6      bad       <--
chromium@472855,v8@cd1325a890      38729003 +- 6407613      6      bad
chromium@472855,v8@9fd599ef98      38578183 +- 2969892      6      bad
chromium@472856                    38672410 +- 395624       6      bad
chromium@472857                    37198151 +- 3229672      6      bad
chromium@472859                    37694319 +- 3489421      6      bad
chromium@472862                    37942701 +- 3568223      6      bad
chromium@472868                    36504045 +- 3797275      6      bad
chromium@472979                    36825719 +- 3775768      6      bad

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=pinterest v8.mobile_infinite_scroll-classic_tbmv2

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

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


| 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!

 Issue 724955  has been merged into this issue.

This only effects the classic configuration (which won't be shipped after M59) so closing as wontfix.

 Issue 727516  has been merged into this issue.

 Issue 727516  has been merged into this issue.