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

Issue 755091 link

Starred by 1 user
Status: WontFix
Owner:
dalecur...@chromium.org
Closed: Sep 2017
Cc:
mmoroz@chromium.org
█ msrchandra@chromium.org
wolenetz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Out-of-memory in media_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Aug 14 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4933529673924608

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  media_pipeline_integration_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=433017:433116

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

Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Aug 14 2017

Cc: msrchandra@chromium.org
Labels: M-62 Test-Predator-Wrong
Owner: wolenetz@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "media_pipeline_integration_fuzzer" assigning to the concern owner who might be related.

@wolenetz -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by wolenetz@chromium.org, Aug 14 2017

Cc: wolenetz@chromium.org
Components: Internals>Media
Labels: -Pri-1 Pri-2
Owner: dalecur...@chromium.org
+mmoroz@ and dalecurtis@ --
Like the recent "timeout"  bug 754500 , this one popped up shortly after fixing the seed_corpus for this fuzzer (broken for > 1 month, fixed last week:  bug 751811 ) and also fixing a fuzzer crash regression (broken ~Aug 1, fixed last week:  bug 751011 ).

Looking at the history for this fuzzer, the oom_count has returned to the level it was at before ~Aug 1.

Therefore, I don't think this is P1.

=> Dale for help identifying a possible fix meanwhile.

Comment 3 by wolenetz@chromium.org, Aug 14 2017

Cc: mmoroz@chromium.org
Project Member

Comment 4 by ClusterFuzz, Aug 16 2017

Labels: OS-Mac

Comment 5 by dalecur...@chromium.org, Aug 23 2017 

Looks like an mp4 file causing the OOM in ffmpeg, will have to take a closer look to see if it's something avoidable.

Comment 6 by dalecur...@chromium.org, Sep 30 2017 

Same as  issue 760928 , it's msan only, bump to 4096 due to msan overhead.

Comment 7 by dalecur...@chromium.org, Sep 30 2017

Status: WontFix (was: Assigned)
►

Sign in to add a comment