CHECK failure: LargestAcked(ack_frame) <= unacked_packets_.largest_sent_packet() in quic_sent_p |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4855436821135360 Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: LargestAcked(ack_frame) <= unacked_packets_.largest_sent_packet() in quic_sent_p net::QuicSentPacketManager::OnIncomingAck net::QuicConnection::OnAckFrame Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=519442:519485 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4855436821135360 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 11 2017
Predator and CL could not provide any possible suspects. Using the code search for the file, “quic_sent_packet_manager.cc” assigning to concern owner from GIT blame. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/1468369698895ac22502a47ff52270d71467e05a @jri -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thank You.
,
Dec 14 2017
,
Jan 11 2018
ClusterFuzz has detected this issue as fixed in range 528550:528560. Detailed report: https://clusterfuzz.com/testcase?key=4855436821135360 Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: LargestAcked(ack_frame) <= unacked_packets_.largest_sent_packet() in quic_sent_p net::QuicSentPacketManager::OnIncomingAck net::QuicConnection::OnAckFrame Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=519442:519485 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=528550:528560 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4855436821135360 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.
,
Jan 11 2018
ClusterFuzz testcase 4855436821135360 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by mmoroz@chromium.org
, Dec 11 2017