[FFmpeg-devel] [PATCH] mov demuxer: use int64_t for next_ts (PR #20313)

[muiz2]

PR #20313 opened by muiz2
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20313
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20313.patch

d1b96c380826c505a8c7e655b5ad4fdb0c2de167 fixes some hevc seeking issues
but will int overflow when timestamp is >int_max.


From eddaae989ef0fe6897274bb0662a42b43fd886dd Mon Sep 17 00:00:00 2001
From: Muiz Yusuff <muiz at google.com>
Date: Fri, 22 Aug 2025 01:01:48 +0000
Subject: [PATCH] mov demuxer: use int64_t for next_ts

d1b96c380826c505a8c7e655b5ad4fdb0c2de167 fixes some hevc seeking issues
but will int overflow when timestamp is >int_max.
---
 libavformat/mov.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libavformat/mov.c b/libavformat/mov.c
index e9a582e5aa..ac0c01a67f 100644
--- a/libavformat/mov.c
+++ b/libavformat/mov.c
@@ -11299,7 +11299,8 @@ static int mov_seek_stream(AVFormatContext *s, AVStream *st, int64_t timestamp,
 {
     MOVStreamContext *sc = st->priv_data;
     FFStream *const sti = ffstream(st);
-    int sample, time_sample, ret, next_ts, requested_sample;
+    int sample, time_sample, ret, requested_sample;
+    int64_t next_ts;
     unsigned int i;
 
     // Here we consider timestamp to be PTS, hence try to offset it so that we
-- 
2.49.1