Timeout in mediasource_MP2T_AACLC_AVC_pipeline_integration_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6209912812863488 Fuzzer: libFuzzer_mediasource_MP2T_AACLC_AVC_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: mediasource_MP2T_AACLC_AVC_pipeline_integration_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=539293:539310 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6209912812863488 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 31
tguilbert@, just wondering this change (https://chromium.googlesource.com/chromium/src/+/2f5083869dd554243dbaf08e06b59b9355dfbab0) is related from the above regression range?
,
Oct 31
The change in C#2 could not have caused this regression. => chcunningham@ as part of ffmpeg roll.
,
Oct 31
Dale, Matt - I recall certain "timeout" fuzzer bugs are WAI, but I'm not familiar with the details. Does this fall into that group?
,
Oct 31
Depends on the bug, you need to check if there's an easy way to avoid it by clamping to some sane value based on stream metadata.
,
Dec 1
ClusterFuzz testcase 6209912812863488 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.
,
Today
(15 hours ago)
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by kkaluri@chromium.org
, Oct 29Labels: M-71 Test-Predator-Wrong CF-NeedsTriage