New issue
Advanced search Search tips

Issue 834556 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in net_url_request_ftp_fuzzer

Project Member Reported by ClusterFuzz, Apr 19 2018

Issue description

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

Fuzzer: libFuzzer_net_url_request_ftp_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=550831:550845

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Components: Internals>Network>FTP

Comment 2 by mmenke@chromium.org, Apr 19 2018

Looking at the test file, this is probably another instance of "Fuzzer can DoS PostTask in a memory instrumented build"
Project Member

Comment 3 by ClusterFuzz, Apr 23 2018

ClusterFuzz has detected this issue as fixed in range 552611:552612.

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

Fuzzer: libFuzzer_net_url_request_ftp_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=550831:550845
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=552611:552612

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

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.
Project Member

Comment 4 by ClusterFuzz, Apr 23 2018

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