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/+/a1256c8c08e2e0ebd3145a3e8ea1e1c659f65a19 (Add traffic annotation to Quic Stream Factory Fuzzer.).

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.

I don't think that it would be related to the stated change list. The change list just adds some extra information about the request, and doesn't have any effect on decisions downstream or the path that the process takes on.
If this value is not provided, only some DCHECKS fail on it.

Unable to find actual suspect through code search and also from the provided CL under regression range, hence adding appropriate label and requesting some one from quic team to look in to this issue.

As per below link cc'ing few file owners to check in to this issue.
https://cs.chromium.org/chromium/src/net/quic/OWNERS?sq=package:chromium&dr

Thanks!

ClusterFuzz has detected this issue as fixed in range 550332:550356.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !writer_->IsWriteBlocked() in quic_connection.cc
  net::QuicConnection::OnCanWrite
  net::QuicConnection::WriteAndBundleAcksIfNotBlocked
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=538035:538042
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=550332:550356

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

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

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