Out-of-memory in mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4642015458623488 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=4642015458623488 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 27 2017
,
Sep 30 2017
pnangunoori@, please do not WontFix Out-of-Memory issues unless you are the owner of the target code (//media in this particular case). Matt, this is a top crasher for that particular fuzzer. It happens in 98+% of runs together with issue 767416 .
,
Oct 3 2017
@mmoroz -- Thank you very much for the update. Will follow as mentioned by you, going further.
,
Oct 5 2017
Like bug 770061 , this is an ASAN oom, so we should check if there are sane limits to be applied in this case. => tguilbert@
,
Oct 9 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by pnangunoori@chromium.org
, Sep 27 2017Status: WontFix (was: Untriaged)