Assigning to the concern owner from Find it --

The result is a list of CLs that change the crashed files. 

The result is a list of CLs that change the crashed files. 

Author: thestig
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/4997b22f84307521a62838f874928bf56cd3423c
Time: Tue Jun 07 10:46:22 2016 -0700
Lines 920, 927-931 of file fx_gif.cpp which potentially caused crash are changed in this cl (frame #5, "gif_load_frame"). 

Lines 2168-2169, 2177-2180, 2186-2187 of file fx_codec_progress.cpp which potentially caused crash are changed in this cl (frame #7, "CCodec_ProgressiveDecoder::ContinueDecode"). 

File fx_codec_gif.cpp is changed in this cl (and is part of stack frame #6, "CCodec_GifModule::LoadFrame")
Minimum distance from crash line to modified line: 0. (file: fx_codec_progress.cpp, crashed on: 2177, modified: 2177). 

Author: thestig
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/fcf61b39ee597c73e80ba789833fb7fe49878422
Time: Thu Jun 09 18:29:35 2016 -0700
Lines 2168-2179, 2186-2191 of file fx_codec_progress.cpp which potentially caused crash are changed in this cl (frame #7, "CCodec_ProgressiveDecoder::ContinueDecode").
Minimum distance from crash line to modified line: 0. (file: fx_codec_progress.cpp, crashed on: 2176, modified: 2176).

@thestig -- Could you please take a look into the issue, kindly reassign if it is not related your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 442676:442736.

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

Fuzzer: libfuzzer_pdf_codec_gif_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  pdf_codec_gif_fuzzer
  
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=442676:442736

Minimized Testcase (7.94 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97vezHbecA992fhlIcAPt8kjx2x1TrFDAzb8vDdRFppAOs6BUXZGuG6rArjAsq8txJBUNIq8-4sOm6YHocOj642evMjzx11-Icwu-LuAb3XtMdQetVdd619wyHmbC_Epvi38xroG-Z7vt0KN8X5rYonpilHew?testcase_id=5154697930604544

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

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

npm@ you fixed some other timeout issues yea, could this have been fixed along with them?

Yes, fixed by:
https://pdfium-review.googlesource.com/c/2161/

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