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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiMvKowkM


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

Android Builder

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : (MonochromePublic.apk)
  Metric       : MonochromePublic.apk_Specifics/normalized apk size


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=normalized.apk.size resource_sizes (MonochromePublic.apk)

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988847160038127168

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6570422197288960


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

This is a 39kb increase. 
Almost certainly due to the new dependency on gridlayout appcompat library.

Probably not much we can do here, but I'll let gogerald@ comment at least.

Yes, "gridlayout appcompat library" is needed for the updated UI as mentioned in the CL and gridlayout is a natural choice in that scenario.

FYI: Bisect on sizes doesn't work at the moment.

 crbug.com/678338