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 suspected regression changelists:

Disable QUIC connection migration and binding to default network, when process bound to network. by pauljensen@chromium.org - https://chromium.googlesource.com/chromium/src/+/e01b20f8fd6ffff89a0ddae9c37c479baaee1b44

Move Vary:* handling to HttpVaryData from HttpResponseHeaders::GetFreshnessLifetimes by morlovich@chromium.org - https://chromium.googlesource.com/chromium/src/+/722dc1135f660708e66ca7f47c16256426838f5f

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

pauljensen@ / morlovich@ Could someone please look into this issue?

I don't believe this is serious, but it is a bug. I'll fix.

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

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

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
  net::QuicSession::GetOrCreateDynamicStream
  net::QuicSpdySession::GetSpdyDataStream
  
Sanitizer: address (ASAN)

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

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

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

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