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!

mbarbella@, can you please see if this change (https://chromium.googlesource.com/chromium/src/+/8c591c43c8d508412f44887b7d483003b7ce932b) is related?

Thank you!

Shouldn't be. That CL just enables another UBSan check unrelated to timeouts.

mmoroz@, Just wondering do you have any idea about the right owner?

Must be a bug in lixbml, please assign to libxml OWNERS: https://cs.chromium.org/chromium/src/third_party/libxml/OWNERS

dcheng@, just wondering do you have any inputs here?

Thank you!

ClusterFuzz has detected this issue as fixed in range 608446:608451.

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

Fuzzer: libFuzzer_xml_parser_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  xml_parser_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=551565:551569
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=608446:608451

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

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

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