New issue
Advanced search Search tips

Issue 779429 link

Starred by 2 users
Status: Assigned
Owner:
wolenetz@chromium.org
Cc:
kkaluri@chromium.org
wolenetz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Out-of-memory in mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Oct 30 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5186003987070976

Fuzzer: libFuzzer_mediasource_WEBM_OPUS_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_OPUS_VP9_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=5186003987070976

Issue filed automatically.

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

Comment 1 by kkaluri@chromium.org, Oct 30 2017

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

Thank You.

Comment 2 by mlamouri@chromium.org, Oct 30 2017

Components: -Blink>Media Internals>Media>Source
Owner: wolenetz@chromium.org
Assigning to wolenetz@ for triage.

Comment 3 by yini...@chromium.org, Oct 30 2017

Status: Assigned (was: Untriaged)
Project Member

Comment 4 by ClusterFuzz, Nov 16 2017

Labels: OS-Mac

Comment 5 by dalecur...@chromium.org, Aug 3

Labels: Pri-3
Project Member

Comment 6 by ClusterFuzz, Oct 9

Labels: OS-Windows

Comment 7 by manoranj...@chromium.org, Oct 26

Labels: -M-63 -CF-NeedsTriage M-71 M-70
wolenetz@, this is OOM, however it's worth to take a look?
Project Member

Comment 8 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5186003987070976 appears to be flaky, updating reproducibility label.

Comment 9 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
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.

Comment 10 by infe...@chromium.org, 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