Timeout in pdf_codec_jbig2_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5029698710274048 Fuzzer: libFuzzer_pdf_codec_jbig2_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: pdf_codec_jbig2_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5029698710274048 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.
,
Dec 1 2017
As per the Issue 782826 owner, assigning this issue to @npm. @npm-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thanks.
,
Dec 4 2017
,
Jan 15 2018
Re-opening.
,
Feb 16 2018
Assigning all my PDF bugs to dsinclair@ for triaging. Will not be working on PDFium for a month.
,
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 ClusterFuzz
, Nov 30 2017Labels: Test-Predator-Auto-Components