Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

> Predator was unable to identify any culprit changelists for this test case. 

> This issue looks similar to   bug 834557  , hence assigning to thestig@ for more updates.

Thanks!

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium/+/36b3d19281e2911a97d6ce84538a3ae575ac38a7

commit 36b3d19281e2911a97d6ce84538a3ae575ac38a7
Author: Lei Zhang <thestig@chromium.org>
Date: Fri May 04 18:49:57 2018

Check CJBig2_Image is valid before filling.

Skip a lot of work that will all fail anyway.

BUG= chromium:838347 

Change-Id: Iba45120e436b5547e106feb27dadea92cc948258
Reviewed-on: https://pdfium-review.googlesource.com/32053
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Ryan Harrison <rharrison@chromium.org>

[modify] https://crrev.com/36b3d19281e2911a97d6ce84538a3ae575ac38a7/core/fxcodec/jbig2/JBig2_GrdProc.cpp
[modify] https://crrev.com/36b3d19281e2911a97d6ce84538a3ae575ac38a7/core/fxcodec/jbig2/JBig2_GrrdProc.cpp
[modify] https://crrev.com/36b3d19281e2911a97d6ce84538a3ae575ac38a7/core/fxcodec/jbig2/JBig2_TrdProc.cpp
[modify] https://crrev.com/36b3d19281e2911a97d6ce84538a3ae575ac38a7/core/fxcodec/jbig2/JBig2_HtrdProc.cpp

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3a49c5174b1dacd9bf158e0d652baa60021ce7cb

commit 3a49c5174b1dacd9bf158e0d652baa60021ce7cb
Author: pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri May 04 23:23:35 2018

Roll src/third_party/pdfium/ ad1788557..36b3d1928 (1 commit)

https://pdfium.googlesource.com/pdfium.git/+log/ad178855775d..36b3d19281e2

$ git log ad1788557..36b3d1928 --date=short --no-merges --format='%ad %ae %s'
2018-05-04 thestig Check CJBig2_Image is valid before filling.

Created with:
  roll-dep src/third_party/pdfium
BUG= chromium:838347 


The AutoRoll server is located here: https://pdfium-roll.skia.org

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.


TBR=dsinclair@chromium.org

Change-Id: Id353b8ca581db7d5524071241aca74b382bea919
Reviewed-on: https://chromium-review.googlesource.com/1044759
Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#556241}
[modify] https://crrev.com/3a49c5174b1dacd9bf158e0d652baa60021ce7cb/DEPS

ClusterFuzz has detected this issue as fixed in range 556222:556252.

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

Fuzzer: libFuzzer_pdf_codec_jbig2_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=421372:421456
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=556222:556252

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5905784001789952 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.