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

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

Predator has provided one possible suspect

Add Quic Stream Factory Fuzzer by nedwilliamson@gmail.com
   *Suspected changelist touched file(s) in the directory net/quic/chromium, which appears in the stack trace.
   *Suspected changelist touched file(s) associated with the component Internals>Network>QUIC, which we believe is related to this testcase based on information in OWNERS files.

Suspect CL : https://chromium.googlesource.com/chromium/src/+/3d55bbb391a5a2e7ba3dd5c083f46bfdb950adcb

Since the author is present in the owners list, assigning it to the reviewer

rch@-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.


Thank You...

I'm the right person to own this and spent time looking at it yesterday and intend to have a fix today.

ClusterFuzz has detected this issue as fixed in range 519442:519485.

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

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
  net::QuicStream::OnStreamFrame
  net::QuicSpdyStream::OnInitialHeadersComplete
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514627:514664
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=519442:519485

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

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

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