CHECK failure: !(public_submodules_->echo_cancellation->is_enabled() && public_submodules_->ech |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6389429496446976 Fuzzer: libFuzzer_audio_processing_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !(public_submodules_->echo_cancellation->is_enabled() && public_submodules_->ech rtc::FatalMessage::~FatalMessage webrtc::AudioProcessingImpl::ProcessCaptureStreamLocked Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=509892:509921 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6389429496446976 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Oct 24 2017
For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md. The link referenced in the description is no longer valid.
,
Oct 25 2017
The following revision refers to this bug: https://webrtc.googlesource.com/src.git/+/ddfd9c5fd2236c426aead743cc884898fde24f5e commit ddfd9c5fd2236c426aead743cc884898fde24f5e Author: Alex Loiko <aleloi@webrtc.org> Date: Wed Oct 25 12:00:36 2017 Fix AudioProcessing fuzzer crash. When audio_processing_fuzzer runs with 'DCHECK_ALWAYS_ON', it crashes when both AEC and AECM is enabled at the same time. This change detects that case and fixes https://clusterfuzz.com/v2/testcase-detail/6389429496446976. It also removes an unnecessary safeguard that didn't allow fuzzing with 8kHz input signals. Bug: chromium:776358 Change-Id: I33c18a2a235e50ae410f7be24637872823e432eb Reviewed-on: https://webrtc-review.googlesource.com/15320 Reviewed-by: Patrik Höglund <phoglund@webrtc.org> Commit-Queue: Alex Loiko <aleloi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20428} [modify] https://crrev.com/ddfd9c5fd2236c426aead743cc884898fde24f5e/test/fuzzers/audio_processing_fuzzer.cc [modify] https://crrev.com/ddfd9c5fd2236c426aead743cc884898fde24f5e/test/fuzzers/audio_processing_fuzzer_configs.cc
,
Oct 26 2017
ClusterFuzz has detected this issue as fixed in range 511532:511556. Detailed report: https://clusterfuzz.com/testcase?key=6389429496446976 Fuzzer: libFuzzer_audio_processing_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !(public_submodules_->echo_cancellation->is_enabled() && public_submodules_->ech rtc::FatalMessage::~FatalMessage webrtc::AudioProcessingImpl::ProcessCaptureStreamLocked Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=509892:509921 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=511532:511556 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6389429496446976 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Oct 26 2017
ClusterFuzz testcase 6389429496446976 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 7 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Oct 19 2017Owner: ale...@webrtc.org
Status: Assigned (was: Untriaged)