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

Issue 909987 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 910040
Owner:
Last visit > 30 days ago
Closed: Dec 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in net_quic_stream_factory_fuzzer

Project Member Reported by ClusterFuzz, Nov 29

Issue description

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  net_quic_stream_factory_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=611798:611813

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Nov 29

Labels: OS-Windows
Project Member

Comment 2 by ClusterFuzz, Nov 29

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.
Cc: kkaluri@chromium.org
Components: Internals>Network>QUIC
Labels: M-72 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Thanks!
Labels: -CF-NeedsTriage
Owner: fkastenholz@chromium.org
Status: Assigned (was: Untriaged)
Here is the change log: https://chromium.googlesource.com/chromium/src/+log/d02bd04ca519357698a747cf7045644cce5fdc33..5de5c9c198b1eab1892fc8a4644c91e577b9c0db?pretty=fuller&n=10000

fkastenholz@, can you please see if this change (https://chromium.googlesource.com/chromium/src/+/878763bfc11f9506ec00af2b1a565274cb60f93b) is related?

Thank you!
Project Member

Comment 5 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6079747223977984 appears to be flaky, updating reproducibility label.
Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
Mergedinto: 910040
Status: Duplicate (was: Assigned)
Believe this to be the same root cause as 910040 and therefore marking it as a duplicate of 910040
Project Member

Comment 8 by ClusterFuzz, Dec 12

ClusterFuzz has detected this issue as fixed in range 615699:615711.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Fuzz target binary: net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  net_quic_stream_factory_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=611798:611813
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=615699:615711

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

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Sign in to add a comment