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

Issue 805836 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Timeout in blink_html_tokenizer_fuzzer

Project Member Reported by ClusterFuzz, Jan 25 2018

Issue description

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

Fuzzer: libFuzzer_blink_html_tokenizer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

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

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.
 
Cc: brajkumar@chromium.org
Components: Blink>HTML
Labels: -Pri-1 M-66 Test-Predator-Wrong CF-NeedsTriage Pri-2
Unable to find actual suspect through code search and observing no CL under regression range, hence adding appropriate label and leaving it as untriaged.

Thanks!

Comment 2 by tkent@chromium.org, Feb 5 2018

Status: WontFix (was: Untriaged)
According to the report, this is just a flaky timeout.

 Issue 810095  has been merged into this issue.
Project Member

Comment 4 by ClusterFuzz, Feb 8 2018

Labels: OS-Mac
 Issue 811050  has been merged into this issue.
 Issue 812141  has been merged into this issue.
Project Member

Comment 7 by ClusterFuzz, Feb 15 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6007980542394368 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

Sign in to add a comment