Predator could not provide any possible suspects.

From the below CL observing some changes related to url_parse_proto_fuzzer, hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/11b54cadcd04ea3b5650839abff6a6060d63e978..781e88b47dc0ae3dcdb28e78851942ff32b83506?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/b423745e74dbc212cd2eade952648c166a9b57b5

metzman@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 559994:560055.

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

Fuzzer: libFuzzer_url_parse_proto_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=501770:501826
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=559994:560055

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

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

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