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 OWNERS file / target commit history.

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

Timed out in fxcrt::WideString::operator+= ...

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

commit d4d645abecec0fe2e6477b5928cfa2967675585b
Author: Ryan Harrison <rharrison@chromium.org>
Date: Fri May 25 20:12:39 2018

Reserve space for code words when creating encoder context

During encoding, the code is going to walk through every character in
m_msg and determine what values need to be added to m_codewords. The
ceiling on the number of characters being added to m_codewords is the
length of m_msg, so reserving enought space in advance. This prevents
thrash related to incrementing the string and thus resizing in a tight
loop.

BUG= chromium:846027 

Change-Id: Icefd6955933f8068feeeee6243e430f60c50d747
Reviewed-on: https://pdfium-review.googlesource.com/32990
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>

[modify] https://crrev.com/d4d645abecec0fe2e6477b5928cfa2967675585b/fxbarcode/datamatrix/BC_EncoderContext.cpp

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

commit 57759fab73a5dc3316ba6247b18bd9678b5f8855
Author: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri May 25 21:24:19 2018

Roll src/third_party/pdfium/ 710fa99b0..d4d645abe (1 commit)

https://pdfium.googlesource.com/pdfium.git/+log/710fa99b0bd2..d4d645abecec

$ git log 710fa99b0..d4d645abe --date=short --no-merges --format='%ad %ae %s'
2018-05-25 rharrison Reserve space for code words when creating encoder context

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


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: I26d090f4a72bd512979b45a7799106a90ad1cc68
Reviewed-on: https://chromium-review.googlesource.com/1073680
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@{#562014}
[modify] https://crrev.com/57759fab73a5dc3316ba6247b18bd9678b5f8855/DEPS

ClusterFuzz has detected this issue as fixed in range 562010:562019.

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

Fuzzer: libFuzzer_pdf_cfx_barcode_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  pdf_cfx_barcode_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=468033:468082
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=562010:562019

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

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

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