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

Author: japhet
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/ace017f26fd8cb8d123238e41c2f0e11f5daacd6
Time: Tue Mar 21 21:17:38 2017
Lines 910, 943 of file DocumentLoader.cpp which potentially caused crash are changed in this cl (frame #1, "chrome_child!blink::DocumentLoader::installNewDocument+0x23"; frame #2, "chrome_child!blink::DocumentLoader::replaceDocumentWhileExecutingJavaScriptURL+0x3a"). 

File FrameLoader.cpp is changed in this cl (and is part of stack frame #3, "chrome_child!blink::FrameLoader::replaceDocumentWhileExecutingJavaScriptURL+0xe2"; frame #5, "chrome_child!blink::FrameLoader::prepareRequestForThisFrame+0x3e"; frame #6, "chrome_child!blink::FrameLoader::load+0xb1")
Minimum distance from crash line to modified line: 0. (file: DocumentLoader.cpp, crashed on: 908, modified: 908).

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

ClusterFuzz has detected this issue as fixed in range 461989:462006.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x000000c7
Crash State:
  blink::LocalFrame::setDOMWindow
  blink::DocumentLoader::installNewDocument
  blink::DocumentLoader::replaceDocumentWhileExecutingJavaScriptURL
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=458542:458585
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=461989:462006

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv96Xv1pTTzJ72FhnfEqyY_eUScBlNV-jIDqddUPyL0anvPSr-M-MnFZJRQsx-pkobReXORpeLLNVYEL8DA8aNf1-lZPix5pRVSAcfKZb-THxZiImxU_TFeQspQgBr99LCxJljVZmycGRQXt14yzjMchV2kyADR9VCezMRYVFCfDZzsFCSBJLSuR2QhW7xlcJaC2_ifWRjA-bJbyquw5smo2cKEJM0xZMXTcsSvdgvAyjtkKBD-Xg6hguzbNwd8W53CvBXJFIN12ae4C5N_kykV2EY9uW5Vu-Eh-aTmU2Y82oxJ5yAUFJKRXvyuuGTtDXCRRK7bIWqmuweutPUUzoAd86krCMykKQDzbQTp53n6ZAvgGhFmFH_mpgf_aeN4wdQOHKBGmaO9s5S81AuQC8J2Y8Wv66Pw?testcase_id=6201106310103040


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 6201106310103040 is verified as fixed, so closing issue.

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