-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Video processing hangs indefinitely with corrupted video segments #2283
Comments
|
I cannot reproduce under Linux with version 2.1.2, can you check on your end and verify if the issue still exists. |
@Archkik can you reproduce it with latest version on master ? |
@OsaAjani I tested with MoviePy 2.1.2 on Windows 10, using the same corrupted video sample from my previous comment,and the issue still persists. This time, instead of hanging immediately, it outputs some video information before getting stuck indefinitely. It seems like the behavior has slightly changed, but the underlying issue with corrupted video segments causing the process to freeze remains.
|
For now I simply dont know what we can do about this. Python subprocess read does not seems to implement a timeout and ffmpeg dont seems to raise an error. If someone have an idea fell free to have a go and make a PR ! |
When processing a video containing corrupted segments, the
subclipped
function (and other methods depending onget_frame
) can hang indefinitely without raising an error or timeout. This behavior seems to be caused by the underlyingframe_function
implementation, which does not handle corrupted frames or set a timeout for frame decoding.Expected Behavior
Raise an error indicating that the frame cannot be decoded, or
Raise a Timeout error
Actual Behavior
The function hangs indefinitely without raising an error, likely due to the underlying frame decoding stalling when encountering corrupted frames.
Specifications
The text was updated successfully, but these errors were encountered: