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

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


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

android-nexus5

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

=== 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] Load IC data handlers now support prototype chain checks with global and dictionary objects.
Author  : ishell
Commit description:
  
BUG=v8:5561

Review-Url: https://codereview.chromium.org/2449463002
Cr-Commit-Position: refs/heads/master@{#40626}
Commit  : 6ea4061b8d0e1ace1ca6ef510ea2aaf067e3d8ef
Date    : Thu Oct 27 15:32:51 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@428048                4386354  8.76356  5  good
chromium@428068                4386876  6.9282   5  good
chromium@428078                4386877  7.15542  5  good
chromium@428081                4386874  8.76356  5  good
chromium@428082                4386874  8.76356  5  good
chromium@428082,v8@3a5056a26c  4386877  7.15542  5  good
chromium@428082,v8@6ea4061b8d  4388930  9.63328  5  bad    <--
chromium@428083                4388933  7.15542  5  bad
chromium@428087                4388930  14.3108  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 661484

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:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
Relative Change: 0.06%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4310
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997112933735383664


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

| 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/8996368646777779040

Something is wrong with this bug report:
1) from the graphs I see that overall regression caused by chromium@428087 is about 1%.
2) it was chromium@428048 who caused 9% regression.
3) bisection report in #3 says that my cl caused only 0.06% of a regression.

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 0.28% | 5192796.0 -> 5178428.95238

Suspected Commit Range
  12 commits in range
  https://chromium.googlesource.com/chromium/src/+log/f26c9e0f69d087a9aae02fb1f0955f6e9680949d..fe4803f332531abfe2845daf6655e8977913da59


Revision                           Result                  N
chromium@428048                    5192796 +- 5658.44      21       good
chromium@428048,v8@017f48d221      ---                     ---      build failure
---                                ---                     ---      too many build failures to list
chromium@428048,v8@452c2b3904      ---                     ---      build failure
chromium@428049                    5193571 +- 80.3326      6        bad
chromium@428050                    5192461 +- 6039.98      6        bad
chromium@428051                    5193553 +- 92.376       6        bad
chromium@428053                    5192189 +- 7503.37      6        bad
chromium@428058                    5193549 +- 95.4009      6        bad
chromium@428068                    5192464 +- 6025.37      6        bad
chromium@428087                    5178429 +- 329006       21       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=https.mobile.twitter.com.justinbieber.skip.interstitial.true memory.top_10_mobile_stress

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

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


| 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 benchmark has been removed.