Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Thanks!

metzman@, can you please look into this change (https://chromium.googlesource.com/chromium/src/+/27c6e434cef36ab378012756d372c8741cbd46ce) if possible and see it's related?

Thank you!

This WAI

ClusterFuzz has detected this issue as fixed in range 609613:609615.

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

Fuzzer: libFuzzer_mojo_parse_message_proto_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=545489:545505
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=609613:609615

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

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.