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/+/5c21f3ef93cfe2c7b7578e9726ff3f730db77037 (Delay SwapOut ACK to fix postMessages sent from subframe unload handlers.).

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.

ClusterFuzz has detected this issue as fixed in range 575549:575550.

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

Fuzzer: quic_fuzzer
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result.second. Inserting a duplicate item in render_frame_proxy.cc
  content::RenderFrameProxy::RenderFrameProxy
  content::RenderFrameProxy::CreateFrameProxy
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=571624:571625
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=575549:575550

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

Additional requirements: Requires Gestures

See https://github.com/google/clusterfuzz-tools 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 5353215684771840 is verified as fixed, so closing issue as verified.

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

 Issue 869796  has been merged into this issue.

Looks like this Clusterfuzz repro (which seems to just set window.location to "www.stanford.edu" in a script, combined with some user input) is hitting the race I'm currently fixing in issue 794625, but it's flaky - hence the close in #4.  I tried this on my local Linux box and couldn't repro.  In any case, the fix for issue 794625 should fix this.