Out-of-memory in mediasource_WEBM_VP9_pipeline_integration_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4951342375501824 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=4951342375501824 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 13 2017
Unable to provide possible suspect using Predator, CL and Code Search. Could someone please look into the issue. Thank You...
,
Nov 13 2017
,
Nov 14 2017
P1 bug, give to wolenetz@ to start. matt, please feel free to reassign appropriately.
,
Nov 14 2017
I have a local repro. It looks very much like bug 760928 : MSAN-only repro (not ASAN), and doesn't repro with MSAN if I set -rss_limit_mb=4096. With dcheck_always_on and with -rss_limit_mb=4096, I *do* see the following output log: ...:ERROR:vpx_video_decoder.cc(689)] vpx_codec_decode() error: Memory allocation error And with further local logging, the vpx decode error detail (vpx_error_internal detail) is "Failed to allocate bool decoder 0". cc+=some of the folks from similar bug 760928 . See especially https://bugs.chromium.org/p/chromium/issues/detail?id=760928#c7 and bug 770430. Please reactivate if this shouldn't be treated like bug 760928 .
,
Nov 15 2017
Sounds good, thanks Matt!
,
Nov 21 2017
ClusterFuzz testcase 4951342375501824 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.
,
Nov 27 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dtapu...@chromium.org
, Nov 12 2017