Out-of-memory in mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5760363068129280 Fuzzer: libFuzzer_mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5760363068129280 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
,
Sep 23 2017
,
Sep 30 2017
,
Oct 9 2017
,
Oct 10 2017
Unduping this one since it seems not to have been improved by CL; may be non-histogram related OOM.
,
Oct 24 2017
For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md. The link referenced in the description is no longer valid.
,
Oct 27 2017
+mmoroz@ -- I'm unable to locally reproduce this failure using the provided test case. Further, I suspect Dale's histogram fix fixed at least part of this problem. Is it the case that this OOM bug is not being closed because there is some *other* case causing OOM in the same sanitizer+fuzzer? If so, how can we let those other cases cause new OOM bugs? (close this bug?)
,
Oct 27 2017
Yes, it probably got fixed. The bold text in the issue description says: We will auto-close the bug if the crash is not seen for 14 days. If we look at the crash statistics (at the testcase details page) for the past 21 day, we can see a significant drop on Oct 9-10th: https://screenshot.googleplex.com/NCiC2kACy3k.png However, there are some very rare cases of a similar crash happening, this is why it hasn't been closed automatically. I think we can manually mark it Fixed now.
,
Oct 27 2017
Closing per #8 and offline confirmation w/mmoroz@. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by pnangunoori@chromium.org
, Sep 22 2017