Predator and CL did not find any possible suspects.
Using Code Search for the file, "tif_ojpeg.c" assigning to the concern owner.
Suspecting Commit#
https://pdfium.git.corp.google.com/pdfium.git/+/73debd4d226114b88430f2cc30dac056be5c13f3#

@Nicolas -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

We have a command-line tool to reproduce this crash locally (on Goobuntu) from chromium source code with a single command. It'd really help speed up the development process. The tool is in alpha. Ping tanin@ or everestmz@ if you are interested.

https://pdfium-review.googlesource.com/c/2830/

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

commit b8a9a5a4dc6fddf60fb247db3fca17a42662632a
Author: pdfium-deps-roller <pdfium-deps-roller@chromium.org>
Date: Fri Feb 24 23:38:15 2017

Roll src/third_party/pdfium/ 37e2bd1ac..412fa6533 (2 commits).

https://pdfium.googlesource.com/pdfium.git/+log/37e2bd1acf84..412fa65331cc

$ git log 37e2bd1ac..412fa6533 --date=short --no-merges --format='%ad %ae %s'
2017-02-24 npm Remove repeated flags from CPDF_Font
2017-02-23 npm Libtiff: fix leaking tables in tif_ojpeg.c

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

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/2717533006
Cr-Commit-Position: refs/heads/master@{#452998}

[modify] https://crrev.com/b8a9a5a4dc6fddf60fb247db3fca17a42662632a/DEPS

It's a memory leak and not a regression. We probably don't need this for M57.

ClusterFuzz has detected this issue as fixed in range 452972:453048.

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

Fuzzer: libfuzzer_pdf_codec_tiff_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  OJPEGReadHeaderInfoSecStreamDht
  OJPEGReadHeaderInfoSec
  OJPEGReadHeaderInfo
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=398366:399171
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=452972:453048

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94s51jn3LW82-8NM73ZuETxlFnLsYk2122B8fg07FlDy5GuEjWWJzq8jX5KP2k1wzl_Eafxo80h7g-VXBfZzn0fOhHJi61CbU-kg_nyhT8fA2fVy_75y_7DIzSKSOEh2uLeHpwsjGBCi9OESw_8j3nrz9W6I4COlRJJuYwhpEQ-ZYEPpC8-8VGDaGm4l5zCqWxHuvBt_2XY960FxM4yMy02Je7BMr9MRBvEpU4lkeSLYp10yG_NkEn3_0WQ1fF_q2VELea-TG1Vg9l9clRDo4X6JG1YcPvb8_nIjXJpb_GoximT-nH0WNH6-JE32m9arPR3KGxBqiSIJu-6QlfdBAQqo9x7CEfWtlAhCxwcHk6M97_L89_ElmfPLYlFpMrlo1LXGKxa2PP4k3IMciQ7uB32wjSZfA?testcase_id=6116263182204928


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.