CHECK failure: !(read_side_closed_ && write_side_closed_) in quic_stream.cc |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4562722904866816 Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !(read_side_closed_ && write_side_closed_) in quic_stream.cc net::QuicStream::OnStreamFrame net::QuicSpdyStream::OnInitialHeadersComplete Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=528550:528560 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4562722904866816 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jan 13 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/079ad54e478f307f2113feed39863a266709887c (Add HTTP/2 stream dependency info derived from RequestPriority to QUIC client headers). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Jan 24 2018
ClusterFuzz has detected this issue as fixed in range 531452:531461. Detailed report: https://clusterfuzz.com/testcase?key=4562722904866816 Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !(read_side_closed_ && write_side_closed_) in quic_stream.cc net::QuicStream::OnStreamFrame net::QuicSpdyStream::OnInitialHeadersComplete Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=528550:528560 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=531452:531461 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4562722904866816 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 24 2018
ClusterFuzz testcase 4562722904866816 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 ClusterFuzz
, Jan 13 2018Labels: Test-Predator-Auto-Components