New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 770061 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 767336
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in mediasource_WEBM_VORBIS_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Sep 29 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5802449922424832

Fuzzer: libFuzzer_mediasource_WEBM_VORBIS_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  mediasource_WEBM_VORBIS_pipeline_integration_fuzzer
  
Sanitizer: address (ASAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5802449922424832

Issue filed automatically.

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

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Status: WontFix (was: Untriaged)
Marking this issue as Wont Fix as it is an Out of Memory issue.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Sep 29 2017

Labels: OS-Mac

Comment 3 by mmoroz@chromium.org, Sep 30 2017

Status: Unconfirmed (was: WontFix)
Re-opening the issue, as it has been incorrectly closed as WontFix. Out of Memory issues are valid bugs in most of the cases.

WontFix status might be assigned only by the owner of the target code, if there is no way or no reason to prevent fuzzer from causing OOM crash.

Sometimes we mark OOMs found with MSan as WontFix because MSan has big memory overhead. However, that should not be done without a proper understanding of the target as well as without looking at the crash stats.
 Issue 769177  has been merged into this issue.
 Issue 768195  has been merged into this issue.
 Issue 767417  has been merged into this issue.
 Issue 766640  has been merged into this issue.
Cc: msrchandra@chromium.org pnangunoori@chromium.org
Components: Blink>Media
Labels: Test-Predator-Wrong CF-NeedsTriage
Status: Untriaged (was: Unconfirmed)
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.
Components: -Blink>Media Internals>Media
Cc: wolenetz@chromium.org
Owner: tguilbert@chromium.org
Status: Assigned (was: Untriaged)
This is an ASAN oom, so we should check if there are sane limits to be applied in this case.
Components: Internals>Media>Source
Mergedinto: 767336
Status: Duplicate (was: Assigned)

Sign in to add a comment