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 adding ccs based on suspected regression changelists:

Landing Recent QUIC changes until 3:43 PM, Jun 28, 2018 UTC-4 by hkhalil@google.com - https://chromium.googlesource.com/chromium/src/+/6e297f2577f105e5c028f7abc0a316cab4df74d3

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "quic_packet_creator.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/9182e5eaf31000ca14807a5421482572b0e1b06a

fayang@ -- 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!

Assigning to Frank to see whether this is related with IetfConnectionClose frame. Thanks.

Fixed with update 1140838

ClusterFuzz has detected this issue as fixed in range 576086:576089.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  packet_size_ == length in quic_packet_creator.cc
  quic::QuicPacketCreator::SerializePacket
  quic::QuicPacketCreator::Flush
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=571954:571955
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=576086:576089

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

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

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