thestig@, assigning to you as an author of the fuzzer :)

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

 Bug 641330 ?

Hm, stacktraces have similar frames, most likely the same bug.

Sorry for the wrong component.

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

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

Fuzzer: libfuzzer_sfntly_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  sfntly::GlyphTable::Glyph::Glyph
  sfntly::GlyphTable::CompositeGlyph::CompositeGlyph
  sfntly::GlyphTable::Glyph::GetGlyph
  
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.81 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95lLJTWei_yHuoAAwgyoXo9nzBks_0v0qidD0gBAgQPtHgqJuYxmcvyyl02ZSEUlPC_CpjK09NGIszgZfhWB2ETjfOJUKFvEbGix38eLEQdfsXyDiTDY7D_lkrFJrOom2nGiPcj7xs2rzxlgIAzT1kCT-Id1A?testcase_id=5597387131453440

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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

Duplicating so I don't get extra credits. ;)

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