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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5rCF6ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpuHgvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvyF_QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvffqgsM


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

android-nexus5X
linux-release

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

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


===== SUSPECTED CL(s) =====
Subject : Raster display item lists via a visual rect RTree.
Author  : wkorman
Commit description:
  
Rather than caching and playing back an entire SkPicture
when rastering a display item list for a particular
playback rect, instead retain display items and query
them via an RTree of their visual rects to find and
raster only what's needed.

Display item lists no longer support the notion of a
bounding "layer rect" with mutable origin.

DisplayItemListSettings proto is obsolete after this
change as it's comprised solely of one field to allow
switching whether to use the aforementioned now-deleted
cached SkPicture code path. It will be deleted in a
subsequent patch.

BUG= 529938 
TBR=sadrul
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/1484163002
Cr-Commit-Position: refs/heads/master@{#409291}
Commit  : ccb9e13712b1632b889960d1d85d556c0139fd51
Date    : Tue Aug 02 20:08:52 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@409261  23698363  13101.6  5  good
chromium@409276  23689574  6550.78  5  good
chromium@409284  24083677  874689   5  good
chromium@409288  23695434  6550.78  5  good
chromium@409290  23692504  10357.7  5  good
chromium@409291  35044269  8023.04  5  bad    <--

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 633944

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_tools-memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_tools_gmail
Relative Change: 47.88%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/426
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005355235121710224


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

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