Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

ClusterFuzz testcase 5349030104924160 appears to be flaky, updating reproducibility label.

Nothing to really do here, there are 12000 frames and my desktop manages ~1000fps, probably bots may be slower at some point. +mmoroz if he'd rather we abort the test for clips beyond a certain duration.

If there is an easy way to reject such inputs, it would be nice, but WontFix is also fine, as this seems to be a fairly rare problem as per crash stats.

I think we can check duration before starting preroll, but if the fuzzer ends up fuzzing something outside of our allowed duration, that's something an external reporter might find. Is that really an okay compromise?

Good point! If you see a potential of finding security bugs that aren't reachable with a constrained duration, then we definitely shouldn't do that. Thanks for clarifying that, Dale!