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

Issue 917297 link

Starred by 2 users

Issue metadata

Status: Verified
Owner: ----
Closed: Jan 9
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in net_gzip_source_stream_fuzzer

Project Member Reported by ClusterFuzz, Dec 21

Issue description

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

Fuzzer: libFuzzer_net_gzip_source_stream_fuzzer
Fuzz target binary: net_gzip_source_stream_fuzzer
Job Type: x86_libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  net_gzip_source_stream_fuzzer
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 21

Cc: xunji...@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Labels: M-72 Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...
Project Member

Comment 3 by ClusterFuzz, Jan 9

ClusterFuzz has detected this issue as fixed in range 620999:621027.

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

Fuzzer: libFuzzer_net_gzip_source_stream_fuzzer
Fuzz target binary: net_gzip_source_stream_fuzzer
Job Type: x86_libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  net_gzip_source_stream_fuzzer
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=620999:621027

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

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

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

Comment 4 by ClusterFuzz, Jan 9

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