Timeout in mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4791639502749696 Fuzzer: libFuzzer_mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4791639502749696 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. We will auto-close the bug if the crash is not seen for 14 days.
,
Sep 21 2017
,
Sep 21 2017
Looks quite similar in debug logs to bug 766472 .
,
Sep 21 2017
,
Sep 21 2017
,
Sep 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/194995c434ed179b0b2cba1269a2f4fd1d4dbcae commit 194995c434ed179b0b2cba1269a2f4fd1d4dbcae Author: Matt Wolenetz <wolenetz@chromium.org> Date: Thu Sep 21 23:13:44 2017 MSE+SRC=: Let early PITB::FailTest() during PITB::Start*() stop the Start*() Modifies PITB::StartPipelineWithMediaSource() to let any PITB::OnEnded() or PITB()::OnError() stop the run loop and let the method return. In cases where OnError (like that triggered if EME is indicated in init segment -> PITB::FailTest()) or OnEnded occur prior to pipeline completing start-up, this avoids one kind of fuzzer timeout. Also includes addition of PITB helpers to assist common "RunUntilIdle" scenarios and refactoring of PITB to use those helpers. Also changes the SRC= PITB::StartInternal() to similarly allow early fuzzer EME callback to quit the run-loop early, possibly mitigating any similar timeouts in SRC= media_pipeline_integration_fuzzer. BUG= 766472 , 766669 Change-Id: I8307db26828eaf04ae92dc1dbee4fa6969c5dd37 Reviewed-on: https://chromium-review.googlesource.com/677774 Reviewed-by: Dan Sanders <sandersd@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#503605} [modify] https://crrev.com/194995c434ed179b0b2cba1269a2f4fd1d4dbcae/media/test/pipeline_integration_test_base.cc [modify] https://crrev.com/194995c434ed179b0b2cba1269a2f4fd1d4dbcae/media/test/pipeline_integration_test_base.h
,
Sep 21 2017
#6 should fix this. Pending CF verification...
,
Dec 1
ClusterFuzz has detected this issue as fixed in range 503598:503620. Detailed report: https://clusterfuzz.com/testcase?key=4791639502749696 Fuzzer: libFuzzer_mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer Sanitizer: address (ASAN) Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=503598:503620 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4791639502749696 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. |
||||
►
Sign in to add a comment |
||||
Comment 1 by pnangunoori@chromium.org
, Sep 20 2017Labels: Test-Predator-Wrong
Owner: wolenetz@chromium.org
Status: Assigned (was: Untriaged)