Timeout in neteq_rtp_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5295569282269184 Fuzzer: libFuzzer_neteq_rtp_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: neteq_rtp_fuzzer Sanitizer: undefined (UBSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5295569282269184 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
Handing this over to hlundin@ as well. Since there are two cases of timeouts for neteq they might be related, somehow. Doesn't look like they're touching the same code paths, though.
,
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
Will take a look. This is probably very similar to https://bugs.chromium.org/p/chromium/issues/detail?id=802245 for which I have a fix in the making.
,
Feb 26 2018
,
Feb 26 2018
The following revision refers to this bug: https://webrtc.googlesource.com/src.git/+/06fa1539f8bd3fb1652305f2569fa6a7ab333bef commit 06fa1539f8bd3fb1652305f2569fa6a7ab333bef Author: Henrik Lundin <henrik.lundin@webrtc.org> Date: Mon Feb 26 10:49:20 2018 neteq_rtp_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:802193 Change-Id: Id32174611fadb480f4e2c6b4f553a2ba0fa5b493 Reviewed-on: https://webrtc-review.googlesource.com/57580 Commit-Queue: Henrik Lundin <henrik.lundin@webrtc.org> Reviewed-by: Alex Loiko <aleloi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22182} [modify] https://crrev.com/06fa1539f8bd3fb1652305f2569fa6a7ab333bef/test/fuzzers/neteq_rtp_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