Predator could not provide any possible suspects.

From the below CL observing some changes related to 'gurl_fuzzer' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/e4d09a45c75e412138f0fc74a26a6efdf05a6fa9..36664eb429a6dbe6e8e487c025409fdee445c304?pretty=fuller&n=10000

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

Abhishek@ -- 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 550253:550265.

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

Fuzzer: libFuzzer_gurl_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=545414:545428
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=550253:550265

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

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

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