Out-of-memory in pdfium_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6399049122185216 Fuzzer: libfuzzer_pdfium_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: pdfium_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=462700:462742 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94sBU04-a8b8jPfWc54RMDmsMIAXOWXPOYdbcMxQ2hyWJ5zIYZtI7mcX7G3s_md5Wnp6dqJRY2z_d8XpJdspdYjB4pWOf-SmS2JyckKJR0qcheILgtUe_zZuycQofPJLTlijVqlQ8KnLvz4r4RQFe9cRfW-dwwmvrSCeLZ5Xfu0dEZa8kiO9xRaG46oVxwWitU3-RKCQ7yNcKONe1y9PeAWJUukO4lj0E6_xlR70c3LNYirVRI4xbHTr10A01uyAhRubrjMKy6ppIRPK9FBAokbn2-35HMqPZeLH76DP5zEEd3zdxVuOdaaQpT-l_8Uz83fd44RN5xPtOrtbzt5XmJR75MRBm0FiIo4Ex61fJw9HicH9cA?testcase_id=6399049122185216 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Apr 8 2017
ClusterFuzz has detected this issue as fixed in range 462742:462744. Detailed report: https://clusterfuzz.com/testcase?key=6399049122185216 Fuzzer: libfuzzer_pdfium_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: pdfium_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=462700:462742 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=462742:462744 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94sBU04-a8b8jPfWc54RMDmsMIAXOWXPOYdbcMxQ2hyWJ5zIYZtI7mcX7G3s_md5Wnp6dqJRY2z_d8XpJdspdYjB4pWOf-SmS2JyckKJR0qcheILgtUe_zZuycQofPJLTlijVqlQ8KnLvz4r4RQFe9cRfW-dwwmvrSCeLZ5Xfu0dEZa8kiO9xRaG46oVxwWitU3-RKCQ7yNcKONe1y9PeAWJUukO4lj0E6_xlR70c3LNYirVRI4xbHTr10A01uyAhRubrjMKy6ppIRPK9FBAokbn2-35HMqPZeLH76DP5zEEd3zdxVuOdaaQpT-l_8Uz83fd44RN5xPtOrtbzt5XmJR75MRBm0FiIo4Ex61fJw9HicH9cA?testcase_id=6399049122185216 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.
,
Apr 8 2017
ClusterFuzz testcase 6399049122185216 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Apr 10 2017
Don't see anything that w ould have fixed this.
,
May 1 2017
,
May 2 2017
Bulk-WontFixing these bugs. This was a bug on ClusterFuzz side, see bug 717534. We will start seeing new testcases auto-filed in a day or two. We can't leave these open as ClusterFuzz won't autoverify them after ClusterFuzz-Wrong label.
,
Sep 18 2017
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by msrchandra@chromium.org
, Apr 7 2017Labels: Test-Predator-Wrong M-59
Owner: dsinclair@chromium.org
Status: Assigned (was: Untriaged)