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

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


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

android-nexus7v2

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@431187  2365402  48.1996  5  good
chromium@431335  2392669  911.41   5  bad
chromium@431483  2393377  911.41   5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 665355

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_lazors
Relative Change: 1.18%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3477
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995940363266121696


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

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

The test timed out after an hour. I'm not sure if this is expected; most of the other runs took ~45 minutes. We have some other instances of this in bug 664765. Going to try re-running.

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

It's the "missing story filter" in auto-launched bisects. Will try to get to fix that one today.

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


===== SUSPECTED CL(s) =====
Subject : [stubs] Port KeyedStoreIC_Megamorphic stub to Turbofan
Author  : jkummerow
Commit description:
  
BUG=v8:5269,v8:5561

Review-Url: https://codereview.chromium.org/2444353002
Cr-Commit-Position: refs/heads/master@{#40896}
Commit  : 5c03cb79228e4312e9722e46c681c0632eb55f2b
Date    : Thu Nov 10 14:23:57 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@431187                2365412  60.2495  8  good
chromium@431261                2363555  8.76356  5  good
chromium@431298                2363543  39.3548  5  good
chromium@431300                2363554  7.15542  5  good
chromium@431300,v8@cc2a2771a6  2363552  0.0      5  good
chromium@431300,v8@5c03cb7922  2392327  39.3548  5  bad    <--
chromium@431300,v8@25d2268ecc  2395822  15637.3  5  bad
chromium@431301                2393307  3488.36  5  bad
chromium@431303                2392327  39.3548  5  bad
chromium@431308                2392310  48.1996  5  bad
chromium@431317                2392327  39.3548  5  bad
chromium@431335                2396460  18492.3  5  bad
chromium@431483                2393017  74.4903  5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 665355

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=load.games.lazors system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_lazors
Relative Change: 1.17%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3479
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995887330372259056


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

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