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

Issue 824639 link

Starred by 1 user
Status: WontFix
Owner:
█ servolk@chromium.org
Last visit > 30 days ago
Closed: Apr 2018
Cc:
█ brajkumar@chromium.org
solenberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Timeout in media_es_parser_mpeg1audio_fuzzer

Project Member Reported by ClusterFuzz, Mar 22 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5515915643584512

Fuzzer: libFuzzer_media_es_parser_mpeg1audio_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  media_es_parser_mpeg1audio_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=523270:523295

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

Issue filed automatically.

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

Comment 1 by brajkumar@chromium.org, Mar 22 2018

Cc: brajkumar@chromium.org
Components: Blink>WebAudio
Labels: -Type-Bug M-66 Test-Predator-Wrong CF-NeedsTriage Type-Bug-Regression
Unable to find actual suspect through code search and also observing no related changes under regression range, hence adding appropriate label and requesting someone from blink team to look in to this issue.

Thanks!

Comment 2 by rtoy@chromium.org, Mar 22 2018

Components: -Blink>WebAudio Internals>Media
Moving to Internals>Media for further triage; this isn't a WebAudio issue.

Comment 3 by yini...@chromium.org, Mar 23 2018

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

Comment 4 by dalecur...@chromium.org, Mar 23 2018

Labels: -Pri-1 Pri-2
Owner: servolk@chromium.org
Not that important and only on Chromecast, so => servolk.
Project Member

Comment 5 by ClusterFuzz, Apr 19 2018

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

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

Sign in to add a comment