CHECK failure: connected_ in quic_connection.cc |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5734317388726272 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: connected_ in quic_connection.cc quic::QuicConnection::OnPaddingFrame quic::QuicFramer::ProcessIetfFrameData Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=612289:612292 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5734317388726272 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Jan 14
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Jan 14
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/1dac18b6bea776bba894b08ce76909ad88455836 (Landing recent QUIC changes until Mon Nov 19 19:05:54 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. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Jan 14Labels: Test-Predator-Auto-Components