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

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


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

Android Builder

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


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


To Run This Test
  src/build/android/resource_sizes.py --chromium-output-directory {CHROMIUM_OUTPUT_DIR} --chartjson {CHROMIUM_OUTPUT_DIR}/apks/MonochromePublic.apk

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

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


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

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

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

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


To Run This Test
  src/build/android/resource_sizes.py --chromium-output-directory {CHROMIUM_OUTPUT_DIR} --chartjson {CHROMIUM_OUTPUT_DIR}/apks/MonochromePublic.apk

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

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


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

Expected, AFAIK

And just to be extra sure: this is used on Android?

Yes, freetype and harfbuzz both are used on all platforms now, including Android.

The additional binary size originates from additional logic that is getting build in FreeType for autohinting based on HarfBuzz information and the hb-ft-* functions. I believe this is used on Android as well in certain cases, but I'll try to double check it.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ba0e6cd12bf6f5e864e1f60993ceafef3f4a7cae

commit ba0e6cd12bf6f5e864e1f60993ceafef3f4a7cae
Author: drott <drott@chromium.org>
Date: Wed May 24 09:08:34 2017

Do not build FreeType with HarfBuzz support on Android

Originally, building FreeType with HarfBuzz, helped improve autohinting
on Linux, see  issue 617168 . However, the performance impact we observe
on Android does not seem to justify running autohinting with HarfBuzz
support on Android.

BUG= 722980 ,  724095 

Review-Url: https://codereview.chromium.org/2896203002
Cr-Commit-Position: refs/heads/master@{#474221}

[modify] https://crrev.com/ba0e6cd12bf6f5e864e1f60993ceafef3f4a7cae/third_party/freetype/BUILD.gn
[modify] https://crrev.com/ba0e6cd12bf6f5e864e1f60993ceafef3f4a7cae/third_party/freetype/include/freetype-custom-config/ftoption.h

ba0e6cd12bf6 reduced this by 4.1kb if I am reading the graphs correctly. Marking as WontFix again, since this a temporary situation and some binary size is recovered for now. We hope to be able to enable this on Android again to fix autohinting issues on Android low resolution displays.