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 adding ccs based on suspected regression changelists:

Do not force a started reader to start reading when migrate to a probing socket. by zhongyi@chromium.org - https://chromium.googlesource.com/chromium/src/+/d3d5f5023f75dfda721f62fb40e5ee80e3ce16e3

Add experiment of switching the client to GOAWAY when path degrading is detected. by renjietang@chromium.org - https://chromium.googlesource.com/chromium/src/+/a5722ccf3852547206c6c95e84fc0a95b4376068

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

With reference to the  Issue 874466 , assigning it to zhongyi@

zhongyi@ Could you please look into it.

ClusterFuzz has detected this issue as fixed in range 599903:599904.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !(read_side_closed_ && write_side_closed_) in quic_stream.cc
  quic::QuicStream::OnStreamFrame
  quic::QuicSpdyStream::OnInitialHeadersComplete
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=581969:581979
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=599903:599904

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

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

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