Issue metadata
Sign in to add a comment
|
Timeout in audio_decoder_fuzzer |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5146367492882432 Fuzzer: libFuzzer_audio_decoder_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: audio_decoder_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=546309:546321 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5146367492882432 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jun 20 2018
This issue looks similar to bug 827204 , hence assigning to the same owner for more updates. liberato@ Could you please take a look in to this issue? Thanks!
,
Jun 20 2018
i'll see if the fix from bug 827204 also applies here, and merge back to 68 if so.
,
Jun 20 2018
i think this is unrelated. the other bug is for flac, this is not. though i also don't know for sure that it's a bug; mine does complete after 25-30 seconds.
,
Jul 19
This bug has a stale milestone. Please close appropriately, update the milestone and set P1/P2, or drop the milestone and set as P3. I'll automatically punt these issues to M70 next week otherwise.
,
Jul 27
These issues have seen no update and have stale milestones, dropping priority and removing milestone.
,
Oct 9
,
Dec 1
ClusterFuzz testcase 5146367492882432 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 14
ClusterFuzz has detected this issue as fixed in range 616464:616465. Detailed report: https://clusterfuzz.com/testcase?key=5146367492882432 Fuzzer: libFuzzer_audio_decoder_fuzzer Fuzz target binary: audio_decoder_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: audio_decoder_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=546309:546321 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=616464:616465 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5146367492882432 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 14
ClusterFuzz testcase 5146367492882432 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Jun 19 2018Labels: ClusterFuzz-Auto-CC