Timeout in pdf_fm2js_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5502004226162688 Fuzzer: libFuzzer_pdf_fm2js_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: pdf_fm2js_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5502004226162688 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.
,
Oct 30 2017
,
Nov 7 2017
,
Nov 8 2017
This is another example where the input isn't valid FormCalc, so the processing should be halting relatively quickly, instead of producing JS. The FormCalc stack has significant issues with grammar conformance that need to be addressed.
,
Nov 8 2017
,
Jan 6 2018
,
Feb 1 2018
FormCalc things
,
Apr 17 2018
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by pnangunoori@chromium.org
, Oct 30 2017Components: Internals>Plugins>PDF
Labels: Test-Predator-Wrong
Owner: rharrison@chromium.org
Status: Assigned (was: Untriaged)