Issue metadata
Sign in to add a comment
|
Out-of-memory in mediasource_WEBM_OPUS_pipeline_integration_fuzzer |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6660018190680064 Fuzzer: libFuzzer_mediasource_WEBM_OPUS_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: mediasource_WEBM_OPUS_pipeline_integration_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6660018190680064 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 30 2017
Re-opening the issue, as it has been incorrectly closed as WontFix. Out of Memory issues are valid bugs in most of the cases. WontFix status might be assigned only by the owner of the target code, if there is no way or no reason to prevent fuzzer from causing OOM crash. Sometimes we mark OOMs found with MSan as WontFix because MSan has big memory overhead. However, that should not be done without a proper understanding of the target as well as without looking at the crash stats.
,
Oct 6 2017
Issue 766492 has been merged into this issue.
,
Oct 6 2017
Unable to provide possible suspect using Predator, CL and Code Search. Could someone please look into the issue. Thank You.
,
Oct 6 2017
,
Oct 6 2017
,
Oct 6 2017
,
Oct 9 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Sep 22 2017