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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi6XszQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq_GHvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi62X_wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgq5zN5QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg696_tAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg693WuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg69uSuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6-Cb4wgM


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

android-nexus6

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

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

Hi aelias@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 : Revert "Getting rid of DelegatedFrameData"
Author  : aelias
Commit description:
  
This reverts commit 4ba3a0e9d06bf66b3d900fec44bcf8ee4a2964a2, which
caused a browser-animation framerate regression on Android.

NOTRY=true
TBR=boliu@chromium.org,danakj@chromium.org,fsamuel@chromium.org,dtrainor@chromium.org,piman@chromium.org,reveman@chromium.org,sky@chromium.org,tsepez@chromium.org
BUG= 663516 , 653741 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2503203002
Cr-Commit-Position: refs/heads/master@{#432390}
Commit  : eb9ecefc55d1e3cf8498d0865568097fb9bbf285
Date    : Wed Nov 16 06:29:13 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@432147  22317440  209217   8  good
chromium@432331  22106880  471440   8  good
chromium@432378  22277504  349740   8  good
chromium@432384  22242560  394855   8  good
chromium@432387  22249728  451624   8  good
chromium@432389  22201600  491033   8  good
chromium@432390  24131584  191332   5  bad    <--
chromium@432401  24181965  181097   5  bad
chromium@432423  24136499  102281   5  bad
chromium@432514  24311398  207008   5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 667318

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=browse.news.hackernews system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_news/browse_news_hackernews
Relative Change: 8.93%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2767
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995370125437811872


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

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

That was just a revert of a recently landed patch, presumably the memory win will come back on the reland.