-
Notifications
You must be signed in to change notification settings - Fork 517
fix: CEA-708 segmentation faults on MP4 files #1729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
CCExtractor CI platform finished running the test files on linux. Below is a summary of the test results, when compared to test for commit 6300bb7...:
NOTE: The following tests have been failing on the master branch as well as the PR:
Congratulations: Merging this PR would fix the following tests:
All tests passing on the master branch were passed completely. Check the result page for more info. |
CCExtractor CI platform finished running the test files on windows. Below is a summary of the test results, when compared to test for commit 6300bb7...:
Your PR breaks these cases:
NOTE: The following tests have been failing on the master branch as well as the PR:
Congratulations: Merging this PR would fix the following tests:
It seems that not all tests were passed completely. This is an indication that the output of some files is not as expected (but might be according to you). Check the result page for more info. |
prateekmedia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
In raising this pull request, I confirm the following (please check boxes):
My familiarity with the project is as follows (check one):
Certain MP4 files under the general category have been segfaulting on the sample platform. The cause was a null pointer dereference in an unsafe rust block here.
The issue was that this particular variable is populated quite late in the MP4 processing chain and hence is sometimes missed. I've modified the code so that its populated right after declaration to fix it.