Predator and CL could not provide any possible suspects.
Using Code Search for the file, "xmlstring.c" assigning to the concern owner who might be related or worked on similar file.

Suspected CL: https://chromium.googlesource.com/chromium/src/+/cc6c1eb1271f22d3d3aaef1d9ae0053dd22b3fa5

dominicc@ -- Could you please look into the issue, kindly re-assign if this is not related to your changes.


Thank You.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

ClusterFuzz has detected this issue as fixed in range 506235:506278.

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

Fuzzer: libFuzzer_libxml_xml_read_memory_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  xmlStrndup
  xmlSplitQName
  xmlSAX2AttributeInternal
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=450688:450717
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=506235:506278

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 6415745360855040 is verified as fixed, so closing issue as verified.

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