Predator could not provide any possible suspects.

From the below CL observing some changes related to 'libfuzzer' hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/c6be58d620359b6c02b4b8b60a554dff2a928e6e..18252f6e125994521e04495b2111ac36ad6a9703?pretty=fuller&n=10000

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

ochang@ -- 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!

My CL may have indeed caused this timeout, as it reduces the optimization level for fuzzing builds.

However, I'm not the right owner for this part of the code. jshin, could you please help with triaging this or taking a look when you have some time? 

ClusterFuzz has detected this issue as fixed in range 583266:583305.

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

Fuzzer: libFuzzer_icu_uregex_open_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

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

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=423384:423408
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=583266:583305

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

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

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