Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on suspected regression changelists:

Simplify FPDF_RenderPage(). by thestig@chromium.org - https://pdfium.googlesource.com/pdfium/+/84144e88da8d2bbd03ba9f8608d5603a18b4d480

Remove unused cpdf_generalstatedata.h by tsepez@chromium.org - https://pdfium.googlesource.com/pdfium/+/341422fe3beb1210b28727d08e1e6f9a6fa4b030

Watch destruction of widgets around OnAAction() method. by tsepez@chromium.org - https://pdfium.googlesource.com/pdfium/+/f8074cefb2f8d947fa83d151bcbe080b485d6e6b

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

https://pdfium-review.googlesource.com/c/pdfium/+/31490

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium/+/7f41d68152885d9b391fd9cc96d9754969b78369

commit 7f41d68152885d9b391fd9cc96d9754969b78369
Author: Lei Zhang <thestig@chromium.org>
Date: Fri Apr 27 14:36:57 2018

Sanitize the SBNUMINSTANCES value in the JBIG2 decoder.

BUG= chromium:837192 

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

[modify] https://crrev.com/7f41d68152885d9b391fd9cc96d9754969b78369/core/fxcodec/jbig2/JBig2_Context.cpp

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

commit 3a094799dfe4dbca1c40fe6f4b5eef00d77ab214
Author: pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri Apr 27 19:46:10 2018

Roll src/third_party/pdfium/ 575f23833..3241bb3e9 (5 commits)

https://pdfium.googlesource.com/pdfium.git/+log/575f238334d1..3241bb3e98c0

$ git log 575f23833..3241bb3e9 --date=short --no-merges --format='%ad %ae %s'
2018-04-27 thestig Fix style for many jbig2 methods.
2018-04-27 thestig Add CJBig2_Image::IsValidImageSize() helper method.
2018-04-27 thestig Sanitize another image size in CJBig2_Context::parseHalftoneRegion().
2018-04-27 rharrison Updated libtiff 4.0.8->4.0.9
2018-04-27 thestig Sanitize the SBNUMINSTANCES value in the JBIG2 decoder.

Created with:
  roll-dep src/third_party/pdfium
BUG= chromium:836872 , chromium:837192 


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: I836d14f6bf7661851deff78a72360d0031648d18
Reviewed-on: https://chromium-review.googlesource.com/1033337
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#554464}
[modify] https://crrev.com/3a094799dfe4dbca1c40fe6f4b5eef00d77ab214/DEPS

ClusterFuzz has detected this issue as fixed in range 554444:554506.

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

Fuzzer: libFuzzer_pdf_codec_jbig2_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
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=554444:554506

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

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 5637807973072896 is verified as fixed, so closing issue as verified.

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