Find it and CL did not find any possible suspects.
Assigning to the concern owner who might be related to Harfbuzz fuzzer.

@mmoroz -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Passing it over to behdad@ as an owner of harfbuzz.

Not sure if there is much else we can do with that content.

Still reproduces for me, all time is spent in OT::apply_lookup

Thanks. Reproduced. Working on it.

Ok, this is a hard one.  Basically, I have to bite the bullet and add an instruction count to the GSUB/GPOS "virtual machine".  There's no other way to meaningfully shut down slow paths without limiting legitimate fonts. Filed tracker bug upstream:

https://github.com/behdad/harfbuzz/issues/429

ClusterFuzz has detected this issue as fixed in range 457466:457505.

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

Fuzzer: libfuzzer_harfbuzz_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  harfbuzz_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=395675:395769
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=457466:457505

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv96BqldRj9ZHSs9uziylBu98PlbMZQ3R_tm_1Hcpoy2O-rg_fhMT2GFu6Iu05X0IDq1sWP740Fx_vK0A0TA2qLcIDVfge4cp8G5PcxFdf_mlDbPkdHYZTZLWDJyjF5EQpcTxnQ3F5KJ95HToLj7Lr-IGbpHB6ziBzF6ZaXnBMqXCZ1rR_zwQo6B7FR7JTHHpx1vAT-jIW58FaKSa-aHGzlfVWzSh4FC3aZS764A15JSRFm70WaX8IDZMiuCwOKUL8FlLvi5GKAI-ZkWL8Mtrc6SorT7rIA0DHYW6qyXTNu7smKZCzt5LtAhaWHaGd1uTiwrp0dcaGCTG77If8JjktLjB7CpsHs_E1YB5uLYTw5dwGcQhjIs?testcase_id=6107935408390144


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 6107935408390144 is verified as fixed, so closing issue.

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