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

Issue 766503 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_OPUS_VP9_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Sep 19 2017

Issue description

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

Fuzzer: libFuzzer_mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  mediasource_WEBM_OPUS_VP9_pipeline_integration_fuzzer
  
Sanitizer: undefined (UBSAN)

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

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 the issue as Wont Fix as this is an Out of Memory issue.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Sep 20 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.
Cc: msrchandra@chromium.org pnangunoori@chromium.org
Labels: Test-Predator-Wrong
Owner: wolenetz@chromium.org
Status: Assigned (was: Unconfirmed)
As per the  Issue 769175  owner, assigning this issue to @wolenetz.
@wolenetz -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.
 Issue 768198  has been merged into this issue.
Cc: dalecur...@chromium.org wolenetz@chromium.org
Components: Internals>Media Internals>Media>Source
Owner: tguilbert@chromium.org
Though not ASAN (rather, ubsan), like  bug 770061  we should check if there are sane limits to be applied in this case (also, this could be duplicate of similar OOMs found in ASAN or other sanitizer runs with similar inputs).
=> tguilbert@
Mergedinto: 767336
Status: Duplicate (was: Assigned)

Sign in to add a comment