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

Issue 808853 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Buried. Ping if important.
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in url_parse_fuzzer

Project Member Reported by ClusterFuzz, Feb 4 2018

Issue description

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

Fuzzer: libFuzzer_url_parse_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

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

Issue filed automatically.

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

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Project Member

Comment 1 by ClusterFuzz, Feb 4 2018

Labels: OS-Mac
Cc: kkaluri@chromium.org
Components: Blink>HTML>Parser
Labels: CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.


Thank You...

Cc: -kkaluri@chromium.org yhirano@chromium.org
Components: -Blink>HTML>Parser
Owner: mkwst@chromium.org
mkwst@: Would you help triage this? (from src/url/OWNERS)
Project Member

Comment 4 by ClusterFuzz, Apr 7 2018

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 6500983228858368 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