mirror of https://github.com/FFmpeg/FFmpeg.git
There is no reason that draining couldn't return an error or two. But some decoders don't handle this very well, and might always return an error. This can lead to API users getting into an infinite loop and burning CPU, because no progress is made and EOF is never returned. In fact, ffmpeg.c contains a hack against such a case. It is made unnecessary with this commit, and removed with the next one. (This particular error case seems to have been fixed since the hack was added, though.) This might lose frames if decoding returns errors during draining.pull/230/merge
parent
3267e1703b
commit
a755b725ec
1 changed files with 3 additions and 3 deletions
Loading…
Reference in new issue