Signed-off-by: Stephen Hutchinson <qyo...@gmail.com>
---
After asking about this and testing with AviSynth+ 3.7.3 and
AviSynth 2.6, it would appear that this isn't necessary.
If it was to handle an edge case and said case reappears,
it can be re-evaluated then.
libavformat/avisynth.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/libavformat/avisynth.c b/libavformat/avisynth.c
index 5d1ecc0bf6..e586fd8ce3 100644
--- a/libavformat/avisynth.c
+++ b/libavformat/avisynth.c
@@ -1085,11 +1085,7 @@ static int avisynth_read_packet(AVFormatContext *s,
AVPacket *pkt)
static av_cold int avisynth_read_close(AVFormatContext *s)
{
- if (ff_mutex_lock(&avisynth_mutex))
- return AVERROR_UNKNOWN;
-
avisynth_context_destroy(s->priv_data);
- ff_mutex_unlock(&avisynth_mutex);
return 0;
}
--
2.43.0
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
