Timeout in neteq_signal_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6434231684431872 Fuzzer: libFuzzer_neteq_signal_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: neteq_signal_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6434231684431872 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.
,
Jan 18 2018
,
Jan 18 2018
,
Jan 18 2018
Could you PTAL. It looks like it's mainly just running WebRtcPcm16b_Encode, which is fairly benign. I guess if the provided length was very large, it could run for a very long time.
,
Feb 23 2018
[Re-triage] Henrik, what's the status here? No work done yet I presume? It's a P1, so it should either get attention or prio lowered.
,
Feb 23 2018
A fix is in the pipeline.
,
Feb 26 2018
The following revision refers to this bug: https://webrtc.googlesource.com/src.git/+/2a6d8642647e7794c9040f3d2e0b3d223d6825e9 commit 2a6d8642647e7794c9040f3d2e0b3d223d6825e9 Author: Henrik Lundin <henrik.lundin@webrtc.org> Date: Mon Feb 26 10:42:30 2018 neteq_signal_fuzzer: limit the fuzzer input size to avoid timeout The length of the fuzzer input can sometimes be really long (more than 600000 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 100000 bytes. NOTRY=TRUE Bug: chromium:802245 Change-Id: Ibe02b6de932d900408f870d9ba440b7b8e08dc0e Reviewed-on: https://webrtc-review.googlesource.com/57180 Commit-Queue: Henrik Lundin <henrik.lundin@webrtc.org> Reviewed-by: Alex Loiko <aleloi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22181} [modify] https://crrev.com/2a6d8642647e7794c9040f3d2e0b3d223d6825e9/test/fuzzers/neteq_signal_fuzzer.cc
,
Mar 6 2018
I believe this should be fixed with the above commit. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by brajkumar@chromium.org
, Jan 17 2018Components: Blink>WebRTC
Labels: Test-Predator-Wrong CF-NeedsTriage