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

Issue 823032 link

Starred by 3 users
Status: WontFix
Owner:
hlundin@chromium.org
Closed: Apr 2018
Cc:
aleloi@chromium.org
█ brajkumar@chromium.org
solenberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Timeout in audio_decoder_isac_fuzzer

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

Fuzzer: libFuzzer_audio_decoder_isac_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=395614:395804

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

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 28 2018

Cc: brajkumar@chromium.org
Components: Internals>Media>Audio
Labels: -Pri-1 M-66 Test-Predator-Wrong Pri-2
Owner: mmoroz@chromium.org
Status: Assigned (was: Untriaged)
Predator could not provide any possible suspects.

From the below CL observing some changes related to 'libfuzzer' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/e0d355a173d0bae9c533fe49ef23258f263e9a8b..61a1c3acf8dd8455bbd5c939c76582de9572445b?pretty=fuller&n=10000

mmoroz@ -- Unable to pinpoint the CL which caused this issue, Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 2 by mmoroz@chromium.org, Mar 28 2018

Cc: aleloi@chromium.org
Owner: hlundin@chromium.org
Alex, Henrik, do you know who can be a good owner for this?
Project Member

Comment 3 by ClusterFuzz, Apr 13 2018

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6476682354229248 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