New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 819652 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

CHECK failure: GetNumDynamicOutgoingStreams() + GetNumLocallyClosedOutgoingStreamsHighestOffset

Project Member Reported by kapishnikov@chromium.org, Mar 7 2018

Issue description

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  GetNumDynamicOutgoingStreams() + GetNumLocallyClosedOutgoingStreamsHighestOffset
  net::QuicSession::GetNumOpenOutgoingStreams
  net::QuicChromiumClientSession::OnClosedStream
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=531452:531790

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Labels: -Stability-Crash -Reproducible -Stability-Memory-AddressSanitizer -Stability-Libfuzzer -Clusterfuzz -Test-Predator-Wrong -Test-Predator-Auto-Components
Components: Internals>Network>QUIC
Cc: brajkumar@chromium.org kapishnikov@chromium.org
 Issue 818437  has been merged into this issue.
Owner: rch@chromium.org
Status: Untriaged
Assigning this bug to rch@ for a proper fix as he was already looking into it (see  Issue 790918 ). This failure periodically appears when someone adds or removes reads from the fuzzer data source. 

Comment 6 by rch@chromium.org, Mar 14 2018

Owner: wangyix@chromium.org
Project Member

Comment 7 by ClusterFuzz, Mar 21 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 6179435955617792 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