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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglvuFsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1uitsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1rKCvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1qzvtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1rK7uwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglv2uvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglsW4sgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglp-ZrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1pylogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1pG3oQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglpyeoAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1tioqAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1sySqQkM


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

android-galaxy-s5
android-nexus5X
android-nexus7v2
android-nexus9
android-one

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@410171  20930560  5943227  8  good
chromium@410193  25366528  0.0      8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 635488

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_os:gpu_memory:gl:proportional_resident_size_avg/load_tools_docs
Relative Change: 14.31%
Score: 0

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


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

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

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


===== SUSPECTED CL(s) =====
Subject : Revert "Raster display item lists via a visual rect RTree."
Author  : wkorman
Commit description:
  
Meta-revert for http://crrev.com/1484163002 due to bugs found in ui/views and
DevTools.

Original change description:

    Raster display item lists via a visual rect RTree.

    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.

Revert "Raster display item lists via a visual rect RTree."

This reverts commit ccb9e13712b1632b889960d1d85d556c0139fd51.

Revert "Don't clear visual rects when finalizing display item lists for now."

This reverts commit 1adf72a0a0a3e04151cc740d15ab19655b1e7e5e.

Revert "Delete obsolete DisplayItemList::ProcessAppendedItem method definition."

This reverts commit f652746f56c59523b0440cf18b769f8ba779d15d.

BUG= 529938 , 633750 , 633869 , 634239 , 634823 , 634959 
TBR=chrishtr@chromium.org,vmpstr@chromium.org,lushnikov@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/2217263003
Cr-Commit-Position: refs/heads/master@{#410190}
Commit  : 490867260447e9360b52d5c03417b000490332e0
Date    : Fri Aug 05 22:27:03 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@410171  34378656  0.0      5  good
chromium@410182  34378656  0.0      5  good
chromium@410188  34378656  0.0      5  good
chromium@410189  34378656  0.0      5  good
chromium@410190  41940640  0.0      5  bad    <--
chromium@410191  41940640  0.0      5  bad
chromium@410193  41940640  0.0      5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635488

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_docs
Relative Change: 22.00%
Score: 99.9

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


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

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