Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/9a9ddbda1675c68ec4573517084804cc5e9b5236 (Output FrameHostMsg_CreateChildFrame parameters  -> reply struct).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

This crash occurs very frequently on mac platform and is likely preventing the fuzzer bj_broddelwerk from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.

Please take a look as this is marked as beta blocker for M-73.

ClusterFuzz has detected this issue as fixed in range 622606:622619.

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

Fuzzer: bj_broddelwerk
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  params.interface_provider.is_bound() in render_frame_impl.cc
  content::RenderFrameImpl::RenderFrameImpl
  content::CreateWebFrameTestProxy
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=622038:622048
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=622606:622619

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

See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

The suspected change has been reverted. Will investigate the causes separately.

ClusterFuzz testcase 5486471234191360 is verified as fixed, so closing issue as verified.

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

ClusterFuzz has detected this issue as fixed in range 622606:622619.

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

Fuzzer: bj_broddelwerk
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  params.interface_provider.is_bound() in render_frame_impl.cc
  content::RenderFrameImpl::RenderFrameImpl
  content::CreateWebFrameTestProxy
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=622038:622048
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=622606:622619

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

See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.