Timeout in pdf_cmap_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5111017037889536 Fuzzer: libFuzzer_pdf_cmap_fuzzer Fuzz target binary: pdf_cmap_fuzzer Job Type: x86_libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: pdf_cmap_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5111017037889536 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Jan 14
Unable to provide possible suspect using Predator, CL and Code Search. With reference to the Issue 881678 , CC'ing it to the rharrison@ for further triage.
,
Jan 14
No longer working on PDFium, forwarding to the thestig@ for triage.
,
Jan 16
The input is rather big but does not seem to add much value.
,
Jan 16
(6 days ago)
The following revision refers to this bug: https://pdfium.googlesource.com/pdfium/+/b440777fde3300145493ca117c556409db7261c0 commit b440777fde3300145493ca117c556409db7261c0 Author: Lei Zhang <thestig@chromium.org> Date: Wed Jan 16 19:30:47 2019 Limit pdf_cmap_fuzzer input to 256 KB. Larger inputs are unlikely to do anything interesting with CPDF_CMap::LoadEmbedded(). BUG= chromium:921373 Change-Id: I51adc25a316d5d8828418e3325bd37be3ec71395 Reviewed-on: https://pdfium-review.googlesource.com/c/48350 Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> [modify] https://crrev.com/b440777fde3300145493ca117c556409db7261c0/testing/fuzzers/pdf_cmap_fuzzer.cc
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e0cff9d23c63d20cba60375a84e5c94cc9974378 commit e0cff9d23c63d20cba60375a84e5c94cc9974378 Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Date: Wed Jan 16 23:31:18 2019 Roll src/third_party/pdfium f054f62ad178..28cfe34a89f2 (4 commits) https://pdfium.googlesource.com/pdfium.git/+log/f054f62ad178..28cfe34a89f2 git log f054f62ad178..28cfe34a89f2 --date=short --no-merges --format='%ad %ae %s' 2019-01-16 tsepez@chromium.org Remove unreachable code paths in cxfa_document_parser.cpp 2019-01-16 tsepez@chromium.org Tidy CXFA_EventParam 2019-01-16 thestig@chromium.org Limit pdf_cmap_fuzzer input to 256 KB. 2019-01-16 thestig@chromium.org Improve LoadCIDType0Font test to check dictionary entry types. Created with: gclient setdep -r src/third_party/pdfium@28cfe34a89f2 The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG= chromium:921373 TBR=dsinclair@chromium.org Change-Id: I772168457ab44bfa8d06ede1f0edf9a79ebd3ae9 Reviewed-on: https://chromium-review.googlesource.com/c/1415972 Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#623448} [modify] https://crrev.com/e0cff9d23c63d20cba60375a84e5c94cc9974378/DEPS
,
Jan 17
(6 days ago)
ClusterFuzz has detected this issue as fixed in range 623417:623458. Detailed report: https://clusterfuzz.com/testcase?key=5111017037889536 Fuzzer: libFuzzer_pdf_cmap_fuzzer Fuzz target binary: pdf_cmap_fuzzer Job Type: x86_libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: pdf_cmap_fuzzer Sanitizer: address (ASAN) Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=623417:623458 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5111017037889536 See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jan 17
(6 days ago)
ClusterFuzz testcase 5111017037889536 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Jan 13Labels: ClusterFuzz-Auto-CC