CHECK failure: decoder_delay_ < original_frame_count in audio_discard_helper.cc |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6684477320593408 Fuzzer: libfuzzer_media_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: decoder_delay_ < original_frame_count in audio_discard_helper.cc media::AudioDiscardHelper::ProcessBuffers media::FFmpegAudioDecoder::FFmpegDecode Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=437773:438087 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6684477320593408 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
May 3 2017
Will take a look, seems like it maybe should just be <= but will have to recall the discard helper code.
,
May 5 2017
ClusterFuzz has detected this issue as fixed in range 469306:469316. Detailed report: https://clusterfuzz.com/testcase?key=6684477320593408 Fuzzer: libfuzzer_media_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: decoder_delay_ < original_frame_count in audio_discard_helper.cc media::AudioDiscardHelper::ProcessBuffers media::FFmpegAudioDecoder::FFmpegDecode Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=437773:438087 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=469306:469316 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6684477320593408 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
May 5 2017
ClusterFuzz testcase 6684477320593408 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
May 15 2017
chcunningham@ did anything change on this while I was out? Seems like this is an incorrect result otherwise.
,
May 17 2017
Sorry, not that I'm aware of.
,
May 17 2017
Not sure why this is verified, it trivially repro'd for me, fix here: https://codereview.chromium.org/2884383003
,
May 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6548bcbdb7254440df8aab0fa8d9bc1dc179364e commit 6548bcbdb7254440df8aab0fa8d9bc1dc179364e Author: dalecurtis <dalecurtis@chromium.org> Date: Thu May 18 18:42:05 2017 Replace DCHECK with conditional and error. libfuzzer always finds a way to trigger these; thanks! This replaces a discard helper DCHECK with a conditional failure. BUG= 717775 TEST=fuzzer doesn't check fail anymore. Review-Url: https://codereview.chromium.org/2884383003 Cr-Commit-Position: refs/heads/master@{#472885} [modify] https://crrev.com/6548bcbdb7254440df8aab0fa8d9bc1dc179364e/media/base/audio_discard_helper.cc
,
May 18 2017
,
Sep 18 2017
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by msrchandra@chromium.org
, May 3 2017Labels: Test-Predator-Wrong-CLs M-60
Owner: dalecur...@chromium.org
Status: Assigned (was: Untriaged)