Findit cannot find any culprit.

assigning to /src/third_party/pdfium/OWNERS, requesting to check the issue and help.

npm@ can you take a look?

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

commit 64816da615023d3bb69a30562d7a27fa10da31c2
Author: pdfium-deps-roller <pdfium-deps-roller@chromium.org>
Date: Wed Mar 01 18:25:16 2017

Roll src/third_party/pdfium/ d1aee7ce4..ef8139039 (2 commits).

https://pdfium.googlesource.com/pdfium.git/+log/d1aee7ce4738..ef81390393ef

$ git log d1aee7ce4..ef8139039 --date=short --no-merges --format='%ad %ae %s'
2017-03-01 thestig Fix infinite loops in CPDF_MeshStream.
2017-02-28 npm LibOpenJPEG upstream: check size in opj_j2k_read_siz

Created with:
  roll-dep src/third_party/pdfium
BUG= 690501 , 694042 

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

TBR=dsinclair@chromium.org

Review-Url: https://codereview.chromium.org/2723093003
Cr-Commit-Position: refs/heads/master@{#453976}

[modify] https://crrev.com/64816da615023d3bb69a30562d7a27fa10da31c2/DEPS

ClusterFuzz has detected this issue as fixed in range 453958:453992.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6606211895263232

Fuzzer: libfuzzer_pdf_jpx_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  opj_t1_dec_clnpass
  opj_t1_decode_cblk
  opj_t1_decode_cblks
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=395640:395746
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=453958:453992

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97nFLGuOXUKgQwcBroztN9hGSjRy7jvggPN8I0G_-DpfL56yxfyoFu2Ez7SSS3AF2qKB1WeoLp9vSu0S3zTc-hFS3NZDYQ6Km7W8ldE3Hz28ohLh4nx-uOhRM2niZ0oR9Kji068dYToE8BmLHPUK1SQfu7l8zNQoUOsCxN2PaN5lEEG3wkxs495BHlVd5Gwewnki2-qznRG5v-shn-RB55M5PsugwGr4YvA0XaiM3VqoME3QqoY6BVtyf6YGmdTUUtyhg-05E-OtRnmxlP4VnB-PYh9havd6yZI9BVsgD2nub2MJ2OpEFQPxGSq72ak3aPPOcaVDYm5cnAuA5g3En3unBxSAV7ntqDTEH9zHhqVxVjMCxyRtPC_HJaP4J2BTVwbURXnJNv5NJobRLxefqbXptMv_w?testcase_id=6606211895263232


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 6606211895263232 is verified as fixed, so closing issue.

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

This issue is reported here again  Issue 698526  with same regression range as above comment # 5.Hence reopening this and adding the appropriate labels to it.

 Issue 698526  has been merged into this issue.

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.