Timeout in pdf_codec_jpeg_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6416342731980800 Fuzzer: libFuzzer_pdf_codec_jpeg_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: pdf_codec_jpeg_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=400757:400887 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6416342731980800 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jun 20 2018
Automatically assigning owner based on suspected regression changelist https://pdfium.googlesource.com/pdfium/+/54d027dbbff8a0270531855082e4f61cb457c173 (Fixup LoadImageInfo type checking.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Jun 20 2018
,
Jun 20 2018
,
Jun 20 2018
After profiling this, it looks like it is doing a bunch of calls to consume_data in libjpeg_turbo. The image being rendered isn't huge and given enough time it will finish the fuzz operation, so I think this is just a pathologically bad jpeg for libjpeg_turbo.
,
Oct 21
,
Nov 29
,
Dec 1
ClusterFuzz testcase 6416342731980800 appears to be flaky, updating reproducibility label. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Jun 20 2018Labels: ClusterFuzz-Auto-CC