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

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


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

android-one

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

=== PERF REGRESSION ===


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

Hi yangguo@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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


===== SUSPECTED CL(s) =====
Subject : v8::Private::ForApi should be context-independent.
Author  : yangguo
Commit description:
  
This is done by reimplementing Symbol.for directly on top of
NameDictionary. A nice side effect is the removal of src/js/symbol.js

R=jochen@chromium.org, peria@chromium.org
BUG= chromium:617892 

Review-Url: https://codereview.chromium.org/2551763003
Cr-Commit-Position: refs/heads/master@{#41520}
Commit  : d26cdb7d6f0b327c15cdb866dafbc21c29a65d4d
Date    : Tue Dec 06 13:21:38 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N   Good?
chromium@436716                2783732  41550.7  8   good
chromium@436728                2807785  31857.5  8   good
chromium@436734                2781415  43813.2  8   good
chromium@436736                2805061  102184   12  good
chromium@436736,v8@12cdb31b2f  2790129  37413.2  8   good
chromium@436736,v8@d26cdb7d6f  2881618  36007.6  5   bad    <--
chromium@436736,v8@2da865d8a4  2878796  24774.6  5   bad
chromium@436736,v8@9c9c8d7bb5  2872441  42218.8  5   bad
chromium@436737                2877461  121043   8   bad
chromium@436739                2875908  37152.6  5   bad
chromium@436761                2881373  24452.8  5   bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 672103

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=https.www.google.co.uk.hl.en.q.science memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
Relative Change: 3.51%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1856
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993919551181100000


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

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

Doesn't look like we're gonna make progress on this 8-month-old bug for a 90kib regression, closing.