Crash in gsignal |
||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6014803101614080 Fuzzer: libfuzzer_pdf_codec_bmp_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: UNKNOWN Crash Address: 0x03e900004e98 Crash State: gsignal FX_AllocOrDie bmp_read_header Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=400757:400887 Minimized Testcase (0.12 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96QTAZ1gIl3UJ4t1Zq24oeWrIYD_Rf_b-Kxy58-rHhAVGdZeKbVe_k_vPCBLJAEK9X3ftkDzR8YckCaeSejvVlDDm3HYywauPb7si5ijXmFz2sjTdB0HMCdRgQQj8rSTJXtTFlZuYh4K4p7aPpOsBcbCUrGag?testcase_id=6014803101614080 Filer: kavvaru See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Jul 13 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 14 2016
I guess it should be merged into bug 616667 .
,
Jul 15 2016
,
Jul 16 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by kavvaru@chromium.org
, Jul 13 2016Labels: Te-Logged M-53
Owner: ananta@chromium.org
Status: Assigned (was: Available)