New issue
Advanced search Search tips

Issue 921078 link

Starred by 1 user
Status: Assigned
Owner:
zhongyi@chromium.org
Cc:
nedwilli...@gmail.com
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: !(read_side_closed_ && write_side_closed_) in quic_stream.cc

Project Member Reported by ClusterFuzz, Jan 11 
Detailed report: https://clusterfuzz.com/testcase?key=5176529323294720

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Fuzz target binary: net_quic_stream_factory_fuzzer
Job Type: x86_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
  quic::QuicStream::OnStreamFrame
  quic::QuicSpdyStream::OnInitialHeadersComplete
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
Project Member

Comment 1 by ClusterFuzz, Jan 11

Components: Internals>Network>QUIC
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Jan 11

Cc: nedwilli...@gmail.com
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Comment 3 by kkaluri@chromium.org, Jan 18 (5 days ago)

Cc: kkaluri@chromium.org
Labels: M-72 Test-Predator-Wrong
Owner: zhongyi@chromium.org
Status: Assigned (was: Untriaged)
With reference to the   Issue 874466  , assigning it to zhongyi@

zhongyi@ Could you please look into it.
►

Sign in to add a comment