Out-of-memory in mediasource_WEBM_VP9_pipeline_integration_fuzzer |
|||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5595088802283520 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=5595088802283520 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Apr 3 2018
> This issue looks similar to bug 826042 , since there are no reproducible steps was available it was marked wontfix > This issue has reproducible steps, hence cc'ing to the same owner for more updates. Thanks!
,
Apr 3 2018
,
Apr 12 2018
give to wolenetz@ as per c#2 since he is owner of crbug/826042
,
Oct 9
,
Oct 26
Based on c#3, removing 'CF-NeedsTriage' label.
,
Oct 29
,
Dec 1
ClusterFuzz testcase 5595088802283520 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. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ClusterFuzz
, Mar 29 2018