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

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

Predator and CL could not provide any possible suspects.
Using the code search for the file, “partition_alloc.cc” assigning to concern owner from GIT blame.
Suspecting Commit#
https://pdfium.googlesource.com/pdfium.git/+/79e548eb98caefd3ea0f0e4806a7abca6654e7dc

@palmer-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Probably  bug 780709 . Rerunning CF...

That's not it. May be  bug 781473  then.

Nope, this one is a request to allocate 32 GB of RAM.

https://pdfium-review.googlesource.com/#/c/pdfium/+/17891 maybe

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium/+/064a3e108b2a2aefde6e0be5f7246b02af6f8aab

commit 064a3e108b2a2aefde6e0be5f7246b02af6f8aab
Author: Lei Zhang <thestig@chromium.org>
Date: Tue Nov 07 00:28:58 2017

Prevent an OOM error in libtiff.

BUG= chromium:781582 

Change-Id: I17711956884d1902cbd86f2163155b256402ecda
Reviewed-on: https://pdfium-review.googlesource.com/17891
Reviewed-by: Chris Palmer <palmer@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>

[add] https://crrev.com/064a3e108b2a2aefde6e0be5f7246b02af6f8aab/third_party/libtiff/0028-nstrips-OOM.patch
[modify] https://crrev.com/064a3e108b2a2aefde6e0be5f7246b02af6f8aab/third_party/libtiff/tif_dirread.c
[modify] https://crrev.com/064a3e108b2a2aefde6e0be5f7246b02af6f8aab/third_party/libtiff/README.pdfium

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

commit f3c106b7b62d76fce03cd806ed7dd564a4711782
Author: pdfium-deps-roller@chromium.org <pdfium-deps-roller@chromium.org>
Date: Tue Nov 07 06:29:58 2017

Roll src/third_party/pdfium/ 6c3665776..064a3e108 (1 commit)

https://pdfium.googlesource.com/pdfium.git/+log/6c3665776eb6..064a3e108b2a

$ git log 6c3665776..064a3e108 --date=short --no-merges --format='%ad %ae %s'
2017-11-07 thestig Prevent an OOM error in libtiff.

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


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: Iba42a0b6f40e92a5a070b5b41a0d04fe60be26d2
Reviewed-on: https://chromium-review.googlesource.com/756478
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514413}
[modify] https://crrev.com/f3c106b7b62d76fce03cd806ed7dd564a4711782/DEPS

ClusterFuzz has detected this issue as fixed in range 514408:514418.

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

Fuzzer: libFuzzer_pdf_codec_tiff_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e9000076c2
Crash State:
  pdfium::base::PartitionExcessiveAllocationSize
  pdfium::base::PartitionReallocGeneric
  _TIFFCheckRealloc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=508791:508824
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=514408:514418

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

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

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