Out-of-memory in mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6582014061576192 Fuzzer: libFuzzer_mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: mediasource_MP4_AACLC_AVC_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=6582014061576192 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Feb 9 2018
Predator could not provide any possible suspects. From the below CL observing some changes related to mp4, hence suspecting the same https://chromium.googlesource.com/chromium/src/+log/cfeea62baf5d453735e86895e1f93ce28a920579..38817f6ce6fbcc08bc74ed4f61953d83e4e64f12?pretty=fuller&n=10000 Suspect CL: https://chromium.googlesource.com/chromium/src/+/2ad785825859b6be6964d484a1d6a5f3f2c2ded5 wolenetz@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Thanks!
,
May 13 2018
,
Jul 19
,
Oct 9
,
Dec 1
ClusterFuzz testcase 6582014061576192 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 6
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Feb 9 2018