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

Issue 811627 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Timeout in url_parse_proto_fuzzer

Project Member Reported by ClusterFuzz, Feb 13 2018

Issue description

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

Fuzzer: libFuzzer_url_parse_proto_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=501747:501826

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Cc: brajkumar@chromium.org
Labels: -Type-Bug M-64 Test-Predator-Wrong Type-Bug-Regression
Owner: metzman@chromium.org
Status: Assigned (was: Untriaged)
Predator could not provide any possible suspects.

From the below CL observing some changes related to url_parse_proto_fuzzer, hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/11b54cadcd04ea3b5650839abff6a6060d63e978..781e88b47dc0ae3dcdb28e78851942ff32b83506?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/b423745e74dbc212cd2eade952648c166a9b57b5

metzman@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!
Project Member

Comment 2 by ClusterFuzz, Feb 15 2018

Labels: OS-Mac
Project Member

Comment 3 by ClusterFuzz, May 14 2018

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5242596700717056 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment