Out-of-memory in pdf_codec_png_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6131624508129280 Fuzzer: libFuzzer_pdf_codec_png_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: pdf_codec_png_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=438798:438824 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6131624508129280 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Jul 24 2017
,
Jul 25 2017
,
Jul 27 2017
This crash happens in ~80% of fuzzer runs and prevents the fuzzer from gaining new coverage and performing continuous testing: https://clusterfuzz.com/v2/performance-report/libFuzzer_pdf_codec_png_fuzzer/libfuzzer_chrome_asan/latest I'm a bit out of the context. What is XFA? Is it some legacy stuff that nobody needs anymore, or is it the opposite, something very new that is raw for production and has many bugs?
,
Jul 27 2017
,
Aug 8 2017
XFA is very new, has many bugs and is not yet ready for production.
,
Aug 23 2017
I just landed the bug 729673 fix in PDFium's copy of libpng and that made this bug go away. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by msrchandra@chromium.org
, Jul 24 2017Labels: M-61 Test-Predator-Wrong
Owner: dsinclair@chromium.org
Status: Assigned (was: Untriaged)