[FFmpeg-trac] #11217(ffmpeg:new): Output "-ss" memory consumption regression

[FFmpeg]

#11217: Output "-ss" memory consumption regression
-------------------------------------+-------------------------------------
             Reporter:  Bryce        |                    Owner:  (none)
  Chester Newman                     |
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:  ffmpeg
              Version:  7.1          |               Resolution:
             Keywords:  seek         |               Blocked By:
  seeking                            |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by Bryce Chester Newman):

 Is it reproducible with `ffmpeg -y -v debug -hide_banner -nostdin -nostats
 -i "1951279840.mov" -ss 67 -vframes 1 "!.jpg"`? No, but that is not the
 issue. That command has always worked as expected in FFmpeg 6 and 7. The
 issue is reproducible with `ffmpeg -report -v 9 -loglevel 99 -y -i
 1951279840.mov  \
 -filter_complex
 "[0:v:0]scale='768:432':force_original_aspect_ratio=decrease:force_divisible_by=2[jpg-600];[0:v:0]scale='1280:640'[mp4-640]"
 \
 -map "[jpg-600]" -ss 67 -f image2 -q:v 5 -update 1 -frames:v 1
 /tmp/jpg-600-123456.jpg \
 -map "[mp4-640]" -map_metadata -1 -f mp4 -vcodec libx264 -profile:v main
 -level 3.1 -crf 23 -b:v 2500K -movflags faststart -refs 4 -pix_fmt yuv420p
 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -preset medium
 /tmp/mp4-640-23456.mp4`

 The work around is not a viable work around as this comes with an
 additional cost for us to request the file two or more times when using
 streaming.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11217#comment:13>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker