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

Issue 918255 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Dec 30
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in pdf_font_fuzzer

Project Member Reported by ClusterFuzz, Dec 29

Issue description

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

Fuzzer: libFuzzer_pdf_font_fuzzer
Fuzz target binary: pdf_font_fuzzer
Job Type: x86_libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=619242:619243

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
 
Project Member

Comment 1 by ClusterFuzz, Dec 29

Cc: jochen@chromium.org weili@chromium.org jam@chromium.org caryclark@google.com npm@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 2 by ClusterFuzz, Dec 30

ClusterFuzz has detected this issue as fixed in range 619275:619276.

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

Fuzzer: libFuzzer_pdf_font_fuzzer
Fuzz target binary: pdf_font_fuzzer
Job Type: x86_libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=619242:619243
Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=619275:619276

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

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

Comment 3 by ClusterFuzz, Dec 30

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 5723537889034240 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