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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/32c5a11a4b7afba3eadf5e7c4b497d74ab30b40b (Landing recent QUIC changes until 8:47 PM, Nov 30, 2018 UTC-5).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f9bc7986085e25522083c22f05d573f17b95e398

commit f9bc7986085e25522083c22f05d573f17b95e398
Author: Fan Yang <fayang@chromium.org>
Date: Thu Dec 20 21:51:56 2018

Close QUIC connection if client tries to create a server initiated bidirectional stream in v99.

R=rch@chromium.org

Bug:  913821 
Change-Id: I2ad66cf2740c89fa2aec6ad23614373ccc160866
Reviewed-on: https://chromium-review.googlesource.com/c/1378406
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Fan Yang <fayang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#618342}
[modify] https://crrev.com/f9bc7986085e25522083c22f05d573f17b95e398/net/quic/quic_chromium_client_session.cc

ClusterFuzz has detected this issue as fixed in range 618340:618345.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Fuzz target binary: net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  type == QuicUtils::GetStreamType(id_, session->IsIncomingStream(id_)) (2 vs. 0)1
  quic::QuicStream::QuicStream
  quic::QuicStream::QuicStream
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=615211:615218
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=618340:618345

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5186058108796928 is verified as fixed, so closing issue as verified.

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