Below is the Predator information --
Regression information is not available. The result is the blame information. 

Author: Bo Xu
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/3522876d5291922ddc62bf1b70d02743b0850673
Time: Tue Jul 08 15:30:46 2014 -0700
The CL last changed line 271 of file cmserr.c, which is stack frame 1. 

Author: John Abd-El-Malek
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/5110c4743751145c4ae1934cd1d83bc6c55bb43f
Time: Sat May 17 22:33:34 2014 -0700
The CL last changed line 1356 of file cmslut.c, which is stack frame 2. 

Author: John Abd-El-Malek
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/5110c4743751145c4ae1934cd1d83bc6c55bb43f
Time: Sat May 17 22:33:34 2014 -0700
The CL last changed line 4460 of file cmstypes.c, which is stack frame 3. 

Author: John Abd-El-Malek
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/5110c4743751145c4ae1934cd1d83bc6c55bb43f
Time: Sat May 17 22:33:34 2014 -0700
The CL last changed line 1535 of file cmsio0.c, which is stack frame 4. 

Author: John Abd-El-Malek
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/5110c4743751145c4ae1934cd1d83bc6c55bb43f
Time: Sat May 17 22:33:34 2014 -0700
The CL last changed line 273 of file cmsio1.c, which is stack frame 5. 

Author: John Abd-El-Malek
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/5110c4743751145c4ae1934cd1d83bc6c55bb43f
Time: Sat May 17 22:33:34 2014 -0700
The CL last changed line 608 of file cmscnvrt.c, which is stack frame 6. 

Author: John Abd-El-Malek
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/5110c4743751145c4ae1934cd1d83bc6c55bb43f
Time: Sat May 17 22:33:34 2014 -0700
The CL last changed line 856 of file cmsxform.c, which is stack frame 7.

Suspecting Commit#
https://pdfium.googlesource.com/pdfium.git/+/3522876d5291922ddc62bf1b70d02743b0850673

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

I don't think this is related to any work of mine.

It's also probably not Linux-specific?

npm@ can you take a look?

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

commit 87ba200028c0bebc63355e11a9c5de9211722f32
Author: Nicolas Pena <npm@chromium.org>
Date: Mon May 08 20:47:27 2017

[LCMS] Upstream direct leak fix

This CL applies the following upstream patch:
https://github.com/mm2/Little-CMS/commit/02c95fa76bdc4f73113373070278666f47aff82f

Bug:  chromium:718500 
Change-Id: I7898b22e44a5ea5c0d1c301233037fbaabb8e327
Reviewed-on: https://pdfium-review.googlesource.com/5092
Reviewed-by: dsinclair <dsinclair@chromium.org>
Commit-Queue: dsinclair <dsinclair@chromium.org>

[modify] https://crrev.com/87ba200028c0bebc63355e11a9c5de9211722f32/third_party/lcms2-2.6/README.pdfium
[modify] https://crrev.com/87ba200028c0bebc63355e11a9c5de9211722f32/third_party/lcms2-2.6/src/cmstypes.c
[add] https://crrev.com/87ba200028c0bebc63355e11a9c5de9211722f32/third_party/lcms2-2.6/0019-upstream-direct-leak-Type_MPE_Read.patch

ClusterFuzz has detected this issue as fixed in range 470151:470238.

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

Fuzzer: libfuzzer_pdf_codec_icc_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  _cmsMallocZero
  cmsPipelineAlloc
  Type_MPE_Read
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=470151:470238

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


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

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