New issue
Advanced search Search tips

Issue 796710 link

Starred by 1 user
Status: WontFix
Owner:
wolenetz@chromium.org
Closed: Mar 2018
Cc:
kkaluri@chromium.org
wolenetz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in mediasource_WEBM_VP9_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Dec 20 2017 
Detailed report: https://clusterfuzz.com/testcase?key=6280574464688128

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=6280574464688128

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

Comment 1 by kkaluri@chromium.org, Dec 21 2017

Cc: kkaluri@chromium.org
Components: Internals>Media
Labels: M-64 Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...
Project Member

Comment 2 by ClusterFuzz, Dec 23 2017

Labels: OS-Mac

Comment 3 by yini...@chromium.org, Jan 2 2018

Components: -Internals>Media Internals>Media>Source
Owner: wolenetz@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by brajkumar@chromium.org, Feb 15 2018 

 Issue 812140  has been merged into this issue.
Project Member

Comment 5 by ClusterFuzz, Mar 12 2018

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5834793166831616 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 6 by ClusterFuzz, Mar 19 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6280574464688128 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