Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: mmoroz
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/d61bcad3017676cfbc1a53c65a51ffcef331b56e
Time: Wed Feb 15 15:46:35 2017
Lines 34-41 of file libxml_xml_read_memory_fuzzer.cc which potentially caused crash are changed in this cl (frame #7, "LLVMFuzzerTestOneInput").
Minimum distance from crash line to modified line: 0. (file: libxml_xml_read_memory_fuzzer.cc, crashed on: 34, modified: 34).

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

Should be similar to https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=600 also known as CVE-2017-5969: 
https://bugzilla.gnome.org/show_bug.cgi?id=778519

ClusterFuzz has detected this issue as fixed in range 455109:455254.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5117493904670720

Fuzzer: libfuzzer_libxml_xml_read_memory_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  xmlDumpElementContent
  xmlDumpElementDecl
  xmlBufDumpElementDecl
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=450688:450717
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=455109:455254

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94EkAqSh0poo4mT5zb1L-e0gwy9lhLVeRd7I32xZJnPtNwYPXpAQZ4pGBgr7YfqlD3qnL-QcCqUAAoMlFf1rWpFsyHL1f7sYoTNyY-kiMfRNnARbGoV2WvSod0mSlcofqIILZ27Tbg8LxvZdVz26BRgFn9YeCajKYx9CQT-XOicaqM6ZLqw2zHXJcdExUrhbu1u2H46gyszygu9X3vkjJGc7kjf6rbeXL3dtg1KDDOnqZKc7QK4NYbc0eUeBVCaAaO5lNZSVKFTgYrFMkY0hlo_yqggAiL26D3QxhC6YWfUkyl8IxHmzBRlS-92EGZCa7ClkF_rcgRO5s1Q4q_FZcKwxsUheb55B0XoXAD2IuBq7gUbZgkpOeXpvJWoh2kaZ9CC_uRQPwEW7Z2c0Av_cftc-G3jaw?testcase_id=5117493904670720


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

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