Predator could not provide any possible suspects.

From the below CL observing some changes related to 'hit_test_query_fuzzer' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/af3e961ab018262a08de4b9c73e1ddeefce7160f..cdaf4fa2a13b64f8c11e445034a4c37512eae8a4?pretty=fuller&n=100000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/9d4d1fef05cca5398d6ae8dfbd6c5f552bff6389

sadrul@ -- 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 552276:552277.

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

Fuzzer: libFuzzer_hit_test_query_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=548211:548216
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=552276:552277

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

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

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