MXF: fixed infinite loop in malformed files#2532
Open
TehMrCrowley wants to merge 1 commit intoMediaArea:masterfrom
Open
MXF: fixed infinite loop in malformed files#2532TehMrCrowley wants to merge 1 commit intoMediaArea:masterfrom
TehMrCrowley wants to merge 1 commit intoMediaArea:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While processing malformed MXF files, we observed that MediaInfo enters an infinite loop, repeatedly re-reading the same byte range and never returning from the query operation. This results in the calling application blocking indefinitely.
The issue was reproduced using the current 25.10 master branch. After investigation, we identified the root cause and implemented a fix in our fork.
In addition to resolving the infinite loop condition, we modified the query logic to return false when a malformed MXF structure is detected, allowing the caller to handle the error gracefully instead of hanging.