Out-of-memory in mediasource_WEBM_VP8_pipeline_integration_fuzzer |
|||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5939974070599680 Fuzzer: libFuzzer_mediasource_WEBM_VP8_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_VP8_pipeline_integration_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=499835:499884 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5939974070599680 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 30 2017
Assigning to wolenetz@ for triage.
,
Oct 30 2017
,
Nov 6 2017
,
Aug 3
,
Oct 9
,
Dec 1
ClusterFuzz testcase 5939974070599680 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 5
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by kkaluri@chromium.org
, Oct 30 2017Components: Blink>Media
Labels: M-63 CF-NeedsTriage Test-Predator-Wrong