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

Author: Stefan Zager
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/76a9686cec40a666328e9af2238f6cfabb02ed30
Time: Fri May 26 22:53:17 2017
Lines 1065 of file LocalFrameView.cpp which potentially caused crash are changed in this cl (frame #2, "blink::LocalFrameView::PerformLayout").
Minimum distance from crash line to modified line: 0. (file: LocalFrameView.cpp, crashed on: 1065, modified: 1065).

@Stefan Zager -- 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 477401:477458.

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

Fuzzer: inferno_webbot
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x00000000
Crash State:
  blink::LocalFrameView::PerformLayout
  blink::LocalFrameView::UpdateLayout
  blink::Document::ImplicitClose
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=475181:475209
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=477401:477458

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


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

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