Assigning to concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: Chris Palmer
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/7726a581626bbb72d6ab294ae1adbad4ca10dfb0
Time: Thu Jun 22 10:10:17 2017 -0700
Lines 34-43 of file fx_memory.cpp which potentially caused crash are changed in this cl (frame #5, "FXMEM_DefaultCalloc").
Minimum distance from crash line to modified line: 0. (file: fx_memory.cpp, crashed on: 34, modified: 34).

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

ClusterFuzz has detected this issue as fixed in range 486527:486654.

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

Fuzzer: libFuzzer_pdf_codec_tiff_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900003a59
Crash State:
  pdfium::base::PartitionAllocGenericFlags
  pdfium::base::PartitionAllocGeneric
  FX_SafeAlloc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=481548:482682
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=486527:486654

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


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

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