Timeout in pdf_codec_jbig2_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6398351892545536 Fuzzer: libFuzzer_pdf_codec_jbig2_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: pdf_codec_jbig2_fuzzer Sanitizer: undefined (UBSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6398351892545536 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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. If the fix resolved the issue, please close the bug by marking as Fixed.
,
Aug 17 2017
Stack-overflow, Out of memory and Timeout issues are 'P2'.
,
Aug 30 2017
Predator and CL could not provide any possible suspects. Using Code Search for the file, "pdf_codec_jbig2_fuzzer" assigning to the concern owner who might be related. tsepez -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Aug 30 2017
,
Aug 31 2017
hnakashima@ can you take a look?
,
Sep 13 2017
,
Sep 13 2017
This is a different codec then I thought, so probably unrelated to my JPX change. I haven't been able to reproduce locally either.
,
Sep 18 2017
Cannot reproduce this locally (neither can clusterfuzz apparently). The only reason I can think of for a long execution time here is if the image was large, but the test case image is small (16x150). Closing as not reproducible. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Aug 11 2017