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

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


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

android-nexus9

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N    Good?
chromium@431857  10043010  35539395  100  good
chromium@431872  10479864  34770519  100  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 665320

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2258
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995944510285670240


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5793691996782592

| 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 Tests>AutoBisect.  Thank you!

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

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@431857  N/A   N/A      0  good
chromium@431872  N/A   N/A      0  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 665320

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/background
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2260
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995940383438172256


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5857415487029248

| 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 Tests>AutoBisect.  Thank you!

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

Hi ishell@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : [ic] Support data handlers that represent transitioning stores.
Author  : ishell
Commit description:
  
BUG=v8:5561

Review-Url: https://codereview.chromium.org/2488673004
Cr-Commit-Position: refs/heads/master@{#40946}
Commit  : bcb3af59be2c52ca13a0adae500f042a64093b6d
Date    : Sun Nov 13 09:38:15 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev  N  Good?
chromium@431857                11282019  541582   8  good
chromium@431861                11263770  128821   5  good
chromium@431863                11265328  166379   5  good
chromium@431864                11212954  623704   8  good
chromium@431864,v8@5d3ce7ea4f  11223534  456224   8  good
chromium@431864,v8@bcb3af59be  11762174  561549   8  bad    <--
chromium@431864,v8@a9f553bada  11654429  547577   8  bad
chromium@431865                11678936  410880   8  bad
chromium@431872                11817429  144361   5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 665320

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.en.m.wikipedia.org.wiki.Science memory.top_10_mobile_stress
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science
Relative Change: 4.75%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2261
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995940313970798624


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6389396310327296

| 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 Tests>AutoBisect.  Thank you!

Maybe we will get some memory back once we remove map-specific handler caches.
Or maybe we will decide to cache data handlers too.
Or WontFix.

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

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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg

Revision             Result                    N
chromium@431857      10043010 +- 35539395      100      good
chromium@431872      10479864 +- 34770519      100      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 memory.top_10_mobile_stress

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

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


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

This regression has been included in a stable release and that stable channel is now deprecated. I'm closing this so that we won't have unresponsive performance regressions in the future.