This could happen when there was a frame number gap and frame threading was
used.
This fixes #5458.
Debugging-by: Ronald S. Bultje <rsbul...@gmail.com>
Debugging-by: Justin Ruggles <justin.rugg...@gmail.com>
Signed-off-by: Derek Buitenhuis <derek.buitenh...@gmail.com>
---
libavcodec/h264_slice.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavcodec/h264_slice.c b/libavcodec/h264_slice.c
index a8a8731138..50c5e6b692 100644
--- a/libavcodec/h264_slice.c
+++ b/libavcodec/h264_slice.c
@@ -1424,6 +1424,9 @@ static int h264_field_start(H264Context *h, const
H264SliceContext *sl,
h->short_ref[0]->f->width == prev->f->width &&
h->short_ref[0]->f->height == prev->f->height &&
h->short_ref[0]->f->format == prev->f->format) {
+ ff_thread_await_progress(&prev->tf, INT_MAX, 0);
+ if (prev->f->interlaced_frame)
+ ff_thread_await_progress(&prev->tf, INT_MAX, 1);
av_image_copy(h->short_ref[0]->f->data,
h->short_ref[0]->f->linesize,
(const uint8_t **)prev->f->data,
--
2.11.0
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
