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/+/60637aee0733db686859db89ce72b948364cb20c (Landing Recent QUIC changes until Fri May 25 16:11:25 2018 +0000).

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.

Similar to  crbug.com/850083  and  crbug.com/850476 .  Probably not a security issue since this code is guarded behind a flag that is default disabled.  fkastenholz to confirm.

Agreed with MPW@
See my comments in  crbug.com/850476 

ClusterFuzz has detected this issue as fixed in range 569395:569417.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  quic::QuicSentPacketManager::OnAckFrameEnd
  quic::QuicConnection::OnAckRange
  quic::QuicFramer::ProcessIetfAckFrame
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=564617:564643
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=569395:569417

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

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

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