Automatically applying components based on crash stacktrace and information from OWNERS files.

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3d55bbb391a5a2e7ba3dd5c083f46bfdb950adcb (Add Quic Stream Factory Fuzzer).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Over to Ryan. Hopefully we can get the owner detection sorted out.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ab2fa2647ee5b2dd0e321aedf2a7990bab444f9b

commit ab2fa2647ee5b2dd0e321aedf2a7990bab444f9b
Author: Ryan Hamilton <rch@chromium.org>
Date: Mon Nov 13 18:44:14 2017

Close the connection when a QUIC RST_STREAM is received which contains an invalid final byte offset.

BUG= 782737 

Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I740f9320b8d97e8fe0ca4a4ba7af62579988fb7e
Reviewed-on: https://chromium-review.googlesource.com/764492
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#515991}
[modify] https://crrev.com/ab2fa2647ee5b2dd0e321aedf2a7990bab444f9b/net/quic/core/quic_stream.cc
[modify] https://crrev.com/ab2fa2647ee5b2dd0e321aedf2a7990bab444f9b/net/quic/core/quic_stream_test.cc

ClusterFuzz has detected this issue as fixed in range 515970:515991.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  bytes_consumed_ <= receive_window_offset_ in quic_flow_controller.cc
  net::QuicFlowController::MaybeSendWindowUpdate
  net::QuicFlowController::AddBytesConsumed
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514627:514664
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=515970:515991

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

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.

ClusterFuzz testcase 4561153547304960 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

ClusterFuzz has detected this issue as fixed in range 515970:515991.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  bytes_consumed_ <= receive_window_offset_ in quic_flow_controller.cc
  net::QuicFlowController::MaybeSendWindowUpdate
  net::QuicFlowController::AddBytesConsumed
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514627:514664
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=515970:515991

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

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.