Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Artem Smorodin <artem.smorodin@dacast.com>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH] avformat/hlsenc: limit segments count to search duplicated segments filenames
Date: Sat, 26 Jul 2025 19:09:54 +0300
Message-ID: <4adefa24-a578-4c98-858c-01b52fd021b4@dacast.com> (raw)

This linear search has a complexity of O(n). When ffmpeg attempts to 
parse a playlist containing approximately 100,000 segments, it 
effectively causes a hang for several minutes.

This patch limits the allowed size for duplicate searches to a 
reasonable value. Now it takes between 0.5 and a few seconds (tested on 
different devices) instead of several minutes.

Signed-off-by: Artem Smorodin <artem.smorodin@dacast.com>
---
  libavformat/hlsenc.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index a93d35ab75..d3db83093c 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -1172,7 +1172,7 @@ static int hls_append_segment(struct 
AVFormatContext *s, HLSContext *hls,
      if (hls->use_localtime_mkdir) {
          filename = vs->avf->url;
      }
-    if ((find_segment_by_filename(vs->segments, filename) || 
find_segment_by_filename(vs->old_segments, filename))
+    if (vs->nb_entries <= 5000 && 
(find_segment_by_filename(vs->segments, filename) || 
find_segment_by_filename(vs->old_segments, filename))
          && !byterange_mode) {
          av_log(hls, AV_LOG_WARNING, "Duplicated segment filename 
detected: %s\n", filename);
      }
-- 
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-request@ffmpeg.org with subject "unsubscribe".

                 reply	other threads:[~2025-07-26 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4adefa24-a578-4c98-858c-01b52fd021b4@dacast.com \
    --to=artem.smorodin@dacast.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git