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/+/6ec9d23283acdcfd324420b296373a37343b9417 (Remove code to explicitly connect socket to a default network.).

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.

Suspected changelist[1] shouldn't be the cause of the regression. The change was to deprecate dead code for a finch experiment(which changes socket level behavior only when the flag is on), and there's no behavior change on stream level. 

[1] https://chromium.googlesource.com/chromium/src/+/6ec9d23283acdcfd324420b296373a37343b9417 (Remove code to explicitly connect socket to a default network.).

ClusterFuzz has detected this issue as fixed in range 581969:581979.

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

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=559775:559780
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=581969:581979

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

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

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