New issue
Advanced search Search tips

Issue 770468 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2017
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in harfbuzz_fuzzer

Project Member Reported by ClusterFuzz, Sep 30 2017

Issue description

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

Fuzzer: libFuzzer_harfbuzz_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

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

Issue manually filed by: mmoroz

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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.
 

Comment 1 by mmoroz@chromium.org, Sep 30 2017

Owner: behdad@chromium.org
We cannot reproduce it issue with a single input, but it happens again and again in 70+% of runs: https://clusterfuzz.com/v2/performance-report/libFuzzer_harfbuzz_fuzzer/libfuzzer_chrome_asan/latest

It's a blocker for the fuzz target gaining new coverage.
Project Member

Comment 2 by ClusterFuzz, Oct 1 2017

Labels: OS-Mac
Labels: Test-Predator-Wrong
Status: Assigned (was: Untriaged)
As per the C#1, changing the status to 'Assigned'.

Comment 4 by mmoroz@chromium.org, Oct 24 2017

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.
Project Member

Comment 5 by ClusterFuzz, Dec 23 2017

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