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

Issue 857404 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit 19 days ago
Closed: Jul 13
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in comfort_noise_decoder_fuzzer

Project Member Reported by ClusterFuzz, Jun 28 2018

Issue description

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

Fuzzer: libFuzzer_comfort_noise_decoder_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  comfort_noise_decoder_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=522405:522413

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jun 28 2018

Cc: mflodman@webrtc.org kwiberg@webrtc.org henrika@webrtc.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 2 by ClusterFuzz, Jun 28 2018

Cc: henrik.lundin@webrtc.org
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Create a fuzzer for ComfortNoiseDecoder by henrik.lundin@webrtc.org - https://webrtc.googlesource.com/src/+/5dcbbfd1533bf14efee5b6bd2b879d515d1095c5

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
Owner: hlundin@chromium.org
Status: Assigned (was: Untriaged)
Cc: saza@chromium.org
Project Member

Comment 5 by bugdroid1@chromium.org, Jul 4

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

commit c05bd738d61e3faec79d9d5fd551660a404388c1
Author: Henrik Lundin <henrik.lundin@webrtc.org>
Date: Wed Jul 04 09:21:41 2018

Limit fuzzer input size for comfort noise decoder fuzzer

This avoids fuzzer timeouts on the bot.

NOTRY=True

Bug:  chromium:857404 
Change-Id: I480c53f005536029c667b9f41aab3ecaca14d125
Reviewed-on: https://webrtc-review.googlesource.com/86945
Commit-Queue: Henrik Lundin <henrik.lundin@webrtc.org>
Reviewed-by: Sam Zackrisson <saza@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#23833}
[modify] https://crrev.com/c05bd738d61e3faec79d9d5fd551660a404388c1/test/fuzzers/BUILD.gn
[modify] https://crrev.com/c05bd738d61e3faec79d9d5fd551660a404388c1/test/fuzzers/comfort_noise_decoder_fuzzer.cc

Project Member

Comment 6 by bugdroid1@chromium.org, Jul 4

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/864958009129d62c02ce15aa7232250b411d24c8

commit 864958009129d62c02ce15aa7232250b411d24c8
Author: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Wed Jul 04 17:44:20 2018

Roll src/third_party/webrtc 57900cb93360..f4aeb891b7aa (15 commits)

https://webrtc.googlesource.com/src.git/+log/57900cb93360..f4aeb891b7aa


git log 57900cb93360..f4aeb891b7aa --date=short --no-merges --format='%ad %ae %s'
2018-07-04 magjed@webrtc.org Android: Handle StartRecording() failure gracefully
2018-07-04 eladalon@webrtc.org Make rtc_event_log2text work on stdin if no input file specified
2018-07-04 saza@webrtc.org Fuzz key presses in APM
2018-07-04 mbonadei@webrtc.org Removing warning suppression flags in common_audio/.
2018-07-04 mbonadei@webrtc.org Removing warning suppression flags from pc/.
2018-07-04 henrik.lundin@webrtc.org NetEq fuzzers: Set max length in BUILD config rather than in the code
2018-07-04 devicentepena@webrtc.org AEC3: Reverberation model: Changes on the decay estimation.
2018-07-04 philipel@webrtc.org Add ParsedPayload::video_header() accessor.
2018-07-04 sprang@webrtc.org Add experimental shortened 2-temporal-layer setting
2018-07-04 henrik.lundin@webrtc.org Limit fuzzer input size for comfort noise decoder fuzzer
2018-07-04 philipel@webrtc.org Remove non-implemented function signatures from RtpFrameReferenceFinder.
2018-07-04 mbonadei@webrtc.org Adding CheckNoWarningSuppressionFlagsAreAdded.
2018-07-04 gustaf@webrtc.org AEC3: Simplified suppression gain calculation
2018-07-04 asapersson@webrtc.org webrtcvideoengine_unittest: Use RtpHeaderParser class for parsing rtp header.
2018-07-04 buildbot@webrtc.org Roll chromium_revision 79cbcdf6fb..1a5890105a (572378:572487)


Created with:
  gclient setdep -r src/third_party/webrtc@f4aeb891b7aa

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng

BUG=chromium:none,chromium:none,chromium:857404,chromium:none,chromium:none,chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I12c95d6fada56c5ceff5060115663d69af0d1a2d
Reviewed-on: https://chromium-review.googlesource.com/1126286
Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#572615}
[modify] https://crrev.com/864958009129d62c02ce15aa7232250b411d24c8/DEPS

Status: Fixed (was: Assigned)
Project Member

Comment 8 by ClusterFuzz, Jul 12

Labels: Needs-Feedback
ClusterFuzz testcase 5100593425940480 is still reproducing on tip-of-tree build (trunk).

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
Owner: saza@chromium.org
Status: Assigned (was: Fixed)
=>saza given that hlundin is ooo.
Labels: -Needs-Feedback ClusterFuzz-Wrong
Status: Fixed (was: Assigned)
The corpus on clusterfuzz seems to have accepted the size cap. If something else is the issue, the fuzzer should generate new timeouts.

Sign in to add a comment