Timeout in media_pipeline_integration_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5647920341975040 Fuzzer: libFuzzer_media_pipeline_integration_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: media_pipeline_integration_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5647920341975040 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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. If the fix resolved the issue, please close the bug by marking as Fixed.
,
Aug 15 2017
This may be a duplicate of bug 754500
,
Aug 15 2017
This is a duplicate of bug 754500 : this issue repros locally on linux before https://chromium-review.googlesource.com/614318, but no repro after. Perf profiler report confirms it looks like a duplicate.
,
Feb 12 2018
Unduplicating so that CF has a chance to specifically verify if this is already fixed.
,
Feb 14 2018
ClusterFuzz has detected this issue as fixed in range 494059:494483. Detailed report: https://clusterfuzz.com/testcase?key=5647920341975040 Fuzzer: libFuzzer_media_pipeline_integration_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: media_pipeline_integration_fuzzer Sanitizer: address (ASAN) Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=494059:494483 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5647920341975040 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.
,
Apr 17 2018
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Aug 12 2017