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!

mmoroz@, just wondering if this is related to 'libFuzzer' changes in the above regression range?

I don't think so, I've just changed the instrumentation (i.e. how we compile everything), but didn't really touched any fuzz target. My change likely changed the execution speed of the fuzzers, but that's a price we have to pay for a better instrumentation.

ClusterFuzz has detected this issue as fixed in range 601582:601596.

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

Fuzzer: libFuzzer_net_ftp_directory_listing_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  net_ftp_directory_listing_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=583292:583305
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=601582:601596

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

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

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