Graph: https://chromeperf.appspot.com/group_report?bug_id=629100

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

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


===== SUSPECTED CL(s) =====
Subject : Revert of Re-enable GPU Rasterization for content with any author defined viewport. (patchset #2 id:20001 of https://codereview.chromium.org/2097413003/ )
Author  : picksi
Commit description:
  
Reason for revert:
This has caused an unexpectedly large regression in overall PSS (about 5MB, graph here: https://chromeperf.appspot.com/report?sid=0b072725c25637efb0d3a44383da1e24e42bbb3740a00505e4040af2173423b0&start_rev=402061&end_rev=402790).
The owners are both OOO and this is blocking Android release. This has already been reverted in the release branch but our infrastructure cannot gather data from the branch to confirm that the revert has had the intended result.

This revert will allow us to confirm that this CL was the cause of the regression. Once confirmed (or otherwise) via telemetry dashboards this revert will be re-reverted.

Original issue's description:
> Re-enable GPU Rasterization for content with any author defined viewport.
>
> BUG= 591179 
>
> Committed: https://crrev.com/a017b667a53b3ee5f8bc630be98c37ebf53a2339
> Cr-Commit-Position: refs/heads/master@{#402702}

TBR=aelias@chromium.org,chrishtr@chromium.org,vmiura@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 591179 

Review-Url: https://codereview.chromium.org/2156553002
Cr-Commit-Position: refs/heads/master@{#405750}
Commit  : 10a77702aa0490dfaaa6e354151b24b738474fb4
Date    : Fri Jul 15 13:13:14 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@405745  26233108  0.0      5  good
chromium@405749  26233108  0.0      5  good
chromium@405750  31065144  0.0      5  bad    <--
chromium@405751  31065144  0.0      5  bad
chromium@405752  31065144  0.0      5  bad
chromium@405758  31065144  0.0      5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 629100

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_news-memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_news_reddit
Relative Change: 18.42%
Score: 99.9

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


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

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