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 could not provide any possible suspects.

From the below CL observing some changes related to 'Quic' hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/9784fa2f0eb5d8ec5055c8f79c76f30547b8b896..03742f3117149602b3ccbf5547eadf49eec75cd3?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/7f8dd1e122d3c6568768b42adc405cea866fdb11

kapishnikov@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Copied  issue chromium:818437  to  issue chromium:819652 

This failure existed before (see  issue 790918 ). I have created a copy of this bug, so it is not automatically closed by the fuzzer later without a proper fix.

ClusterFuzz has detected this issue as fixed in range 544635:544640.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  GetNumDynamicOutgoingStreams() + GetNumLocallyClosedOutgoingStreamsHighestOffset
  net::QuicSession::GetNumOpenOutgoingStreams
  net::QuicChromiumClientSession::OnClosedStream
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=531452:531790
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=544635:544640

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

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.