Out-of-memory in mediasource_WEBM_VP9_pipeline_integration_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5024060315795456 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=5024060315795456 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Oct 3 2017
Unable to provide possible suspect using Predator, CL and Code Search. Could someone please look into the issue. Thank You.
,
Oct 3 2017
As per the Issue 760928 owner, assigning this issue to @dalecurtis. @dalecurtis -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thanks.
,
Oct 4 2017
Don't have any plan to fix these under MSAN.
,
Oct 11 2017
ClusterFuzz testcase 5024060315795456 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Oct 2 2017