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

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


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

Android Builder

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

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

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


| 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 Speed>Bisection.  Thank you!

Confirmed, just zooming into the graph shows the the jump came from 453285
https://chromeperf.appspot.com/report?sid=5d55db44beb13bb1e813882381fe82b47aa2934496f2e59840f8ee908da122ca&rev=453285

+simon in case this is interesting (an alert blamed the wrong commit, even when the graph shows it correctly.

Looks like the regression is strictly due to more strings being added. Closing.

Whoops, didn't mean to change the title.
commit link: https://codereview.chromium.org/2703733004