aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/x86/h264_intrapred.asm
diff options
context:
space:
mode:
authorBryan Huh <bryan@box.com>2015-11-11 02:00:21 -0800
committerMichael Niedermayer <michael@niedermayer.cc>2015-11-13 12:43:22 +0100
commitd07585f04add2448c9a8760ba263f7ac64c910c7 (patch)
tree39c53aef39d9e388d930aa075e7b9d8d5ab51e01 /libavcodec/x86/h264_intrapred.asm
parent5324109dd7e1bfc0236bf74a492a66f26289d16e (diff)
downloadffmpeg-d07585f04add2448c9a8760ba263f7ac64c910c7.tar.gz
avformat/async: Fix bug where async could not recover after seek to eof
When async issues its inner seek via ffurl_seek, it treats failures as EOF being reached. This is not consistent with the behavior of other protocols (e.g. http, cache) which continue to tolerate reads after failed seeks, and therefore does not interact correctly with them. A common pattern where this manifests itself is where avio_seek is called with pos to be the end-of-file - the http range-request would fail here, and async would set io_eof_reached to 1. The background thread would then refuse to read more bytes, and subsequent reads would only empty the fifo and end in an error. Presumably the code may have expected subsequent seeks to unset the io_eof_reached but this is not guaranteed to be true - a subsequent seek that lands in the AVIOContext's buffer (the fact that the previously-failed avio_seek leaves the AVIOContext's buffer intact also suggests that follow-up reads are expected to be tolerated) would not be issued to the async_seek function, and when that buffer is drained only async_read calls would follow, leading to the same error just described. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
Diffstat (limited to 'libavcodec/x86/h264_intrapred.asm')
0 files changed, 0 insertions, 0 deletions