Predator, CL and Code Search did not provide any possible suspects.
Assigning to the concern owner who previously worked on similar issues.
dominicc -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Thank you.

For now, fixing libxml leaks are not a priority for Blink.

ClusterFuzz has detected this issue as fixed in range 480737:480767.

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

Fuzzer: libFuzzer_libxml_xml_read_memory_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  xmlNewText
  xmlNewDocText
  xmlStringGetNodeList
  
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=480737:480767

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


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

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