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

Issue 811938 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Timeout in sfntly_fuzzer

Project Member Reported by ClusterFuzz, Feb 13 2018

Issue description

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

Fuzzer: libFuzzer_sfntly_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=536295:536309

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Cc: brajkumar@chromium.org
Components: Internals
Labels: -Pri-1 -Type-Bug M-66 Test-Predator-Wrong Pri-2 Type-Bug-Regression
Owner: thestig@chromium.org
Status: Assigned (was: Untriaged)
Unable to find the suspect through code search and also from the provided CL, hence assigning to @thestig who have worked on similar  issue 803020  and got fixed recently. 

thestig@ Could you please take a look in to this issue?

Thanks!
Components: -Internals Internals>Skia>PDF
Yes, I can look at sfntly_fuzzer issues. Not sure if it is really a regression though. CF may be incorrect.
Project Member

Comment 3 by ClusterFuzz, Feb 20 2018

Labels: OS-Mac
Status: Started (was: Assigned)
Project Member

Comment 5 by bugdroid1@chromium.org, Feb 22 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e18303469043d05e27e125c44161e66a32be28bc

commit e18303469043d05e27e125c44161e66a32be28bc
Author: Lei Zhang <thestig@chromium.org>
Date: Thu Feb 22 03:47:02 2018

Roll DEPS for sfntly 16f3404..2804148

2804148 Handle negative offsets when reading name tables.
f5e0c30 Validate table count in font headers.

BUG= 724890 , 811938 
TBR=behdad@chromium.org

Change-Id: Ie3a073347099b963e38ec80ea5bbaec5c17b49ec
Reviewed-on: https://chromium-review.googlesource.com/930365
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538337}
[modify] https://crrev.com/e18303469043d05e27e125c44161e66a32be28bc/DEPS

Project Member

Comment 6 by ClusterFuzz, Feb 22 2018

ClusterFuzz has detected this issue as fixed in range 538333:538342.

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

Fuzzer: libFuzzer_sfntly_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=536295:536309
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=538333:538342

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

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 7 by ClusterFuzz, Feb 22 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Started)
ClusterFuzz testcase 5356430245494784 is verified as fixed, so closing issue as verified.

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

Sign in to add a comment