Out-of-memory in mediasource_WEBM_VP9_pipeline_integration_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5577811086802944 Fuzzer: libFuzzer_mediasource_WEBM_VP9_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_VP9_pipeline_integration_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=497057:497112 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5577811086802944 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.
,
Oct 18 2017
,
Oct 18 2017
,
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 25 2017
mmoroz@, this is an unreproducible CF report and it's still worth to investigate?
,
Oct 26 2017
Yes, it's worth to investigate as we see it happening again and again
,
Nov 9 2017
Though this particular one happens with MSan and not too often. Plus, it doesn't have a useful stack. I'm WontFix'ing it for now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kkaluri@chromium.org
, Oct 18 2017Components: Blink>Media
Labels: Test-Predator-Wrong CF-NeedsTriage