New issue
Advanced search Search tips

Issue 802968 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 805624

Blocking:
issue 62400



Sign in to add a comment

Timeout in pdf_xml_fuzzer

Project Member Reported by ClusterFuzz, Jan 17 2018

Issue description

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

Fuzzer: libFuzzer_pdf_xml_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

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

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.
 
Project Member

Comment 1 by ClusterFuzz, Jan 17 2018

Components: Internals>Plugins>PDF
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.
Ping! Could anyone let us know is there any latest update available on this issue?

Thanks!
Blocking: 62400
Labels: -Pri-1 Pri-2
Owner: rharrison@chromium.org
Status: Started (was: Untriaged)
This is fuzzer is XFA only. 

I will take look at it while looking into other XFA ClusterFuzzer issues.
Blockedon: 805624
Status: Assigned (was: Started)
Status: WontFix (was: Assigned)
This takes almost 25 seconds in my VM to run. Since the timeout uses walltime, load/statistical variation could explain why this is tripping the timeout. Not much to be done about this.

Sign in to add a comment