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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e3e592e12cd54ba26fb2576bced629bdf88f09c0 (Bundle the test certificate in the QUIC fuzzer at compile time.).

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

Also not serious, but a real bug. I'll fix.

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

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e90000388b
Crash State:
  net::QuicSession::SendRstStream
  net::QuicChromiumClientSession::SendRstStream
  net::QuicSpdyClientSessionBase::ResetPromised
  
Sanitizer: address (ASAN)

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

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

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

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