[FFmpeg-trac] #9073(undetermined:new): ffmpeg memory overflow when trimming 4K clips

[FFmpeg]

#9073: ffmpeg memory overflow when trimming 4K clips
-------------------------------------+-------------------------------------
             Reporter:  andykais     |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  memory       |               Blocked By:
  filter_complex inputs              |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by andykais):

 Can you share what an optimized filter graph would look like richardpl? I
 will submit a different ticket if the problem persists. It is hard to know
 what is un-optimized if you do not explain. If this has to do with using
 overlays as opposed to a "concat" filter, that is because these ffmpeg
 commands are not hand-rolled, but are built using a program. The inputs
 need to be able to be started at any time. This is a simple example  for
 the reproduction.

 Outside of my non-optimized commands though, how is this not a bug? Why
 doesn't trimming clips at input time behave the same as inputting trimmed
 files? There seems to be no reason that the latter should use upwards of
 16GB of ram, while the prior only uses 4GB of ram.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/9073#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker