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

Issue 802149 link

Starred by 1 user
Status: Fixed
Owner:
hlundin@chromium.org
Closed: Mar 2018
Cc:
█ brajkumar@chromium.org
█ saza@chromium.org
henrik.lundin@webrtc.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in comfort_noise_decoder_fuzzer

Project Member Reported by ClusterFuzz, Jan 16 2018 
Detailed report: https://clusterfuzz.com/testcase?key=4584506307903488

Fuzzer: libFuzzer_comfort_noise_decoder_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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.

Comment 1 by brajkumar@chromium.org, Jan 17 2018

Cc: henrik.lundin@webrtc.org brajkumar@chromium.org
Components: Blink>WebRTC
Labels: Test-Predator-Wrong
Owner: saza@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "comfort_noise_decoder_fuzzer.cc" and observed there was some recent changes for the below file.

Suspect CL: https://webrtc.googlesource.com/src.git/+/5dcbbfd1533bf14efee5b6bd2b879d515d1095c5%5E%21/test/fuzzers/comfort_noise_decoder_fuzzer.cc

saza@- 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 hlundin@chromium.org, Jan 17 2018

Cc: saza@chromium.org
Owner: hlundin@chromium.org
Assigning to hlundin (== henrik.lundin@webrtc.org)
Project Member

Comment 3 by ClusterFuzz, Jan 27 2018

Labels: OS-Mac

Comment 4 by hlundin@chromium.org, Feb 26 2018

Status: Started (was: Assigned)
Project Member

Comment 5 by bugdroid1@chromium.org, Feb 26 2018 

The following revision refers to this bug:
  https://webrtc.googlesource.com/src.git/+/151be2dffcc15121e986e5e1a4ffd91ba237fe04

commit 151be2dffcc15121e986e5e1a4ffd91ba237fe04
Author: Henrik Lundin <henrik.lundin@webrtc.org>
Date: Mon Feb 26 10:52:30 2018

comfort_noise_decoder_fuzzer: limit the fuzzer input size to avoid timeout

The length of the fuzzer input can sometimes be really long (more than
1000000 bytes), and this take a very long time to execute. Typically,
the fuzzer times out instead. This change limits the used length of
the fuzzer to 200000 bytes.

NOTRY=TRUE

Bug:  chromium:802149 
Change-Id: Ia9d2f080602bba8ff70c5f0575bb9ecfa99c537c
Reviewed-on: https://webrtc-review.googlesource.com/57581
Commit-Queue: Henrik Lundin <henrik.lundin@webrtc.org>
Reviewed-by: Alex Loiko <aleloi@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#22183}
[modify] https://crrev.com/151be2dffcc15121e986e5e1a4ffd91ba237fe04/test/fuzzers/comfort_noise_decoder_fuzzer.cc

Comment 6 by hlundin@chromium.org, Mar 6 2018

Status: Fixed (was: Started)
I believe this should be fixed with the above commit.
►

Sign in to add a comment