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

Author: csharrison
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/95f01e92e7147bee4e66ce629712fd1f50808936
Time: Mon Apr 24 18:52:35 2017
Files render_frame_impl.cc, render_view_impl.cc are changed in this cl (and is part of stack frame #2, "content::RenderFrameImpl::RenderFrameImpl"; frame #3, "content::RenderFrameImpl::Create"; frame #4, "content::RenderFrameImpl::CreateMainFrame")
Minimum distance from crash line to modified line: 24. (file: render_frame_impl.cc, crashed on: 1176, modified: 1200).

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

+nick to possibly take a look since I am OOO for a few days.

The problem is we're creating a frame with duplicate ids.

ClusterFuzz has detected this issue as fixed in range 476712:476772.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x00000000
Crash State:
  content::RenderFrameImpl::RenderFrameImpl
  content::RenderFrameImpl::Create
  content::RenderFrameImpl::CreateMainFrame
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=434255:434304
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=476712:476772

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


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

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