From the above regression range suspecting the below CL
https://chromium.googlesource.com/chromium/src/+/05192643e8bfe9ece91d32bd6084f5ccfe33f5a4

thestig@, could you please take a look in to this issue?

Thanks!

Need to validate the numSizes field in EblcTable::Builder::Initialize().

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

commit 286c80467ef26401c15d42ad93d26f4c5cac471d
Author: Lei Zhang <thestig@chromium.org>
Date: Sat Jan 20 01:32:20 2018

Roll DEPS for sfntly 2439bd0..16f3404

16f3404 Merge pull request #95 from leizleiz/eblc-validate
bc830a8 Validate EBLC table's numSizes field.
b553114 fix #52 OTS parsing error (#54)
8c0954e Update README.md (#94)
34db4db Document the inactive status of the project (#91)
7c4b837 Fix endless loop in FontMath.log2. (#85)
6b0889d Rescue the old wiki pages from web.archive.org. (#87)

BUG= 803020 
TBR=behdad@chromium.org

Change-Id: Ie849670d0e5f653cdc810ecbe19ab82b09efcbf4
Reviewed-on: https://chromium-review.googlesource.com/877320
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#530719}
[modify] https://crrev.com/286c80467ef26401c15d42ad93d26f4c5cac471d/DEPS

ClusterFuzz has detected this issue as fixed in range 530703:530719.

Detailed report: https://clusterfuzz.com/testcase?key=5493446612877312

Fuzzer: libFuzzer_sfntly_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  sfntly_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=414243:414324
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=530703:530719

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5493446612877312

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5493446612877312 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.