Please note that the crash has been found using a debug version. May be not a valid issue.

May be a variant of  bug 642300 ?

Yeah, looks similar! Does bug_642300.patch fix this one?

I landed the fix for  bug 642300 . I'll just wait a day or two and see what CF says.

ClusterFuzz has detected this issue as fixed in range 416997:417261.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6604922852474880

Fuzzer: libfuzzer_sfntly_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e900006f1a
Crash State:
  sfntly::FontData::FontData
  sfntly::ReadableFontData::ReadableFontData
  sfntly::WritableFontData::WritableFontData
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=414176:414284
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=416997:417261

Minimized Testcase (0.06 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94Ay3xvaRWej1I3PsXyVOFAajFWTVcD0DViMoULuXfPDqMewmiPrqenjdLSz2ukIs9wClBx7fiAOfvjzj5PPswiR1rwqd2h_hz7ynOwTYFMCCFTviqycuBfG5RdOZV06ZKjmAWOzstqh1g_QsITx0cfD31hWA?testcase_id=6604922852474880

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

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot