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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvOTZvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3JeqqAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvN6ioAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvPWVtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvOCnogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3JfgoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvOC9vQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvILiqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvKmopQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvMn3uAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvMmFsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvOD2tQoM


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

android-galaxy-s5
android-nexus5
android-nexus6
android-nexus7v2
android-nexus9

+primiano, picksi as a heads up for a potentially big memory regression.

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

Hi vmpstr@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 : cc: Separate raster and decode prepaint regions.
Author  : vmpstr
Commit description:
  
This patch separates raster and decode distances to be
independent of each other. Specifically, any tile in prepaint
that is further than 1000 screen space pixels from the
viewport will not be rasterized. Instead, we will pull out
the images on those tiles and predecode those instead.

R=enne, ericrk
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review-Url: https://codereview.chromium.org/2007163002
Cr-Commit-Position: refs/heads/master@{#398677}
Commit  : 70a29c1298e666c465a8e75530575eda1aeaa37c
Date    : Wed Jun 08 21:21:04 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@398671  47374.3  481.623  6  good
chromium@398675  47396.2  750.634  5  good
chromium@398676  47545.4  425.727  5  good
chromium@398677  50601.2  760.06   5  bad    <--
chromium@398678  50916.6  701.424  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 618658

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.basic_oopif
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 7.30%
Score: 99.9

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


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

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

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Ping

This is wont fix.  On Android, the renderer memory increases a little, but the total memory decreases by a lot more.

https://chromeperf.appspot.com/report?sid=43f2df3c53feebd218dc9e40262320a9332536533c70b941d4d501f2c09b6d36&start_rev=397703&end_rev=399383

See also: http://crbug.com/624467