Timeout in media_pipeline_integration_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5710106882473984 Fuzzer: libFuzzer_media_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: media_pipeline_integration_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=519945:519980 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5710106882473984 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 3
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/21ece16c7d9e0d06786579e7d86a7993a706f656 (Use video frame duration metadata instead of waiting for 2 frames.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Dec 4
File is just one super long video frame, so I think this is WontFix. We decided that duration suppression would harm fuzzer coverage.
,
Dec 6
,
Dec 8
,
Dec 11
ClusterFuzz testcase 5710106882473984 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Dec 3Labels: ClusterFuzz-Auto-CC