New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 761129 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Out-of-memory in pdf_codec_jbig2_fuzzer

Project Member Reported by ClusterFuzz, Aug 31 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5474476992233472

Fuzzer: libFuzzer_pdf_codec_jbig2_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  pdf_codec_jbig2_fuzzer
  
Sanitizer: memory (MSAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5474476992233472

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.
 
Labels: -Pri-1 Test-Predator-Wrong CF-NeedsTriage Pri-2
Redo task has been performed for new Regression range.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Sep 7 2017

Labels: OS-Mac
Cc: msrchandra@chromium.org kkaluri@chromium.org
Components: Internals>Plugins>PDF
Labels: -CF-NeedsTriage
Status: WontFix (was: Untriaged)
Since redo task has not given any new regression range and there is no sufficient stack trace available for triage, hence marking this issue as Won't Fix

Sign in to add a comment