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:

Stop sending SSLInfo from network service for subframe navigations. by livvielin@chromium.org - https://chromium.googlesource.com/chromium/src/+/139bf442fac22bf19e96704b228f122cd20a7b2b

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.

This is related to a bug in the internal quic code. It has already been fixed but it's under the protection of feature flag. I did some investigation and I think this fuzzer testcase doesn't have the flag turned on. 

With reference to the   Issue 877814  , assigning it to renjietang@

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

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !QuicContainsKey(static_stream_map_, stream_id). Attempt to call GetOrCreateDyna
  quic::QuicSession::GetOrCreateDynamicStream
  quic::QuicSpdySession::GetSpdyDataStream
  
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=6324767861506048

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

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