Skip to content

Conversation

@GiacomoPignoni
Copy link

I've added an additional check on the extracted frameDuration to be sure that it's also positive using CMTIME_IS_POSITIVE_INFINITY

Fix flutter/flutter#151031

Pre-Review Checklist

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

  1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. 2 3

@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to fix a crash caused by a non-positive frameDuration when creating an AVMutableVideoComposition. The proposed change adds a check using CMTIME_IS_POSITIVE_INFINITY. While this prevents the crash for zero-duration values, it is logically incorrect. This check will fail for any valid, positive frame duration that is not positive infinity, causing the code to fall back to a default frame rate for nearly all videos. I've provided a suggestion to use CMTimeCompare to correctly check if the duration is positive, which fixes the crash while preserving the intended behavior.


videoComposition.sourceTrackIDForFrameTiming = videoTrack.trackID;
if (CMTIME_IS_VALID(videoTrack.minFrameDuration)) {
if (CMTIME_IS_VALID(videoTrack.minFrameDuration) && CMTIME_IS_POSITIVE_INFINITY(videoTrack.minFrameDuration)) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

The use of CMTIME_IS_POSITIVE_INFINITY is incorrect for checking if a CMTime value is positive. This macro specifically checks if the time is positive infinity, not whether it's greater than zero. As a result, for any valid video with a finite frame duration (e.g., 1/30s), this condition will be false, and the code will incorrectly fall back to a default frame duration of 30fps.

The correct way to ensure the frameDuration is positive is to compare it with kCMTimeZero.

Suggested change
if (CMTIME_IS_VALID(videoTrack.minFrameDuration) && CMTIME_IS_POSITIVE_INFINITY(videoTrack.minFrameDuration)) {
if (CMTIME_IS_VALID(videoTrack.minFrameDuration) && CMTimeCompare(videoTrack.minFrameDuration, kCMTimeZero) > 0) {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[video_player]Invalid videoComposition may cause the app crash

1 participant