Timeout in mediasource_MP4_AV1_pipeline_integration_fuzzer |
|||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6206367504007168 Fuzzer: libFuzzer_mediasource_MP4_AV1_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: mediasource_MP4_AV1_pipeline_integration_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=578801:578809 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6206367504007168 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 21
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/f2813ce352ac65a2d4259ae7aba9fa739d3903aa (enable av1 playback by default). 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.
,
Oct 22
Wan-Teh, would you take a look at this please?
,
Oct 22
Hi Johann, It seems that the suspected regression CL in comment 2 was committed on July 27 and cherry-picked to branch refs/branch-heads/3497. Why was this bug reported only yesterday? Do you know how to reproduce the test timeout? This bug report looks quite different from the oss-fuzz bugs I have been working on, so I don't know how to reproduce this bug.
,
Oct 22
The regression CL is the first time AV1 was turned on by default. That just means it's existed since the original AV1 commit. The test case appears to be use the mp4 container which makes it tricky to reproduce with aomdec, which only reads .webm/.mkv and .ivf. The initial comment has repro instructions for building within chromium. As for why this was just reported, fuzzing is continuous and can uncover old bugs.
,
Oct 30
,
Dec 1
ClusterFuzz testcase 6206367504007168 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
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ClusterFuzz
, Oct 21Labels: ClusterFuzz-Auto-CC