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

commit b8cc3ad7241229a774e5182c62c4b1f0fc19ac95
Author: Dominik Röttsches <drott@chromium.org>
Date: Fri Oct 06 16:47:09 2017

Add a fuzzer target for HarfBuzzShaper

For now it's not using a corpus since basically any string would work as
a useful input and the input data is interpreted as UTF-32, then
converted to UTF-16. This follow the discussion about raw input in the
HarfBuzz fuzzing bug:
https://github.com/behdad/harfbuzz/issues/139#issuecomment-156182545

Bug:  771594 
Change-Id: Ibf60bb6b67c60131337a712c7b8baf6b5219a52b
Reviewed-on: https://chromium-review.googlesource.com/700375
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#507099}
[modify] https://crrev.com/b8cc3ad7241229a774e5182c62c4b1f0fc19ac95/third_party/WebKit/Source/platform/BUILD.gn
[add] https://crrev.com/b8cc3ad7241229a774e5182c62c4b1f0fc19ac95/third_party/WebKit/Source/platform/fonts/shaping/HarfBuzzShaperFuzzer.cpp