New issue
Advanced search Search tips

Issue 820833 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in harfbuzz_fuzzer

Project Member Reported by ClusterFuzz, Mar 11 2018

Issue description

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

Fuzzer: libFuzzer_harfbuzz_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

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

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=521669:521798

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 11 2018

Components: Blink>Fonts
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Mar 11 2018

Labels: Test-Predator-Auto-Owner
Owner: drott@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/66aaf201efada2d0a2d1f3c090ef4858dd41c392 (Roll HarfBuzz to 1.7.2).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 3 by drott@chromium.org, Mar 12 2018

Labels: Test-Predator-Wrong-CLs
Status: WontFix (was: Assigned)
We are already at HarfBuzz 1.7.6 after
https://chromium-review.googlesource.com/c/chromium/src/+/951736, I'll close this as WontFix, please reopen if the timeout still occurs. 

Project Member

Comment 4 by ClusterFuzz, Mar 19 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6462232674959360 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.
Project Member

Comment 5 by ClusterFuzz, Mar 21 2018

Labels: OS-Linux
 Issue 832829  has been merged into this issue.

Sign in to add a comment