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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/f4683a37ef679c4b1ea669855567a7938724389a (Add a different config param to control connection migration v2 on).

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 571954:571955.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900005b0c
Crash State:
  quic::QuicSession::SendRstStream
  net::QuicChromiumClientSession::SendRstStream
  quic::QuicSpdyClientSessionBase::ResetPromised
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=520730:520767
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=571954:571955

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 5059796638892032 is verified as fixed, so closing issue as verified.

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