[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):

 Ok thank you. I am using the latest version (4.3.1) but I could try
 building from source if the amix bug is not part of the latest release.

 > Have you tried also different container?

 The same bug occurs with an mp4 container generated with the following
 command:
 {{{
 ffmpeg -i 'Norway 4K - Winter in Norway - Relaxing Music with AMAZING
 Beautiful Nature and sound-voprky8BrPw.mkv' -c copy -map 0 'Norway 4K -
 Winter in Norway - Relaxing Music with AMAZING Beautiful Nature and sound-
 voprky8BrPw.mp4'
 }}}

 If this is a poorly formed filtergraph, could you guide me in how to make
 it better? Apologies, I know this is not the place for assistance. One
 idea I have is to replace `setpts`/`asetpts` with `-itsoffset` and
 `enable='between(...)'`. This pretty much requires that I use `overlay`
 rather than `xstack` though, since the "enable" arg is tied to each input.

 Other than that I can only think to be smarter about using
 xstack/hstack/vstack and concat filters. The issue is that some of the
 time, users will want videos to be rendered on a timeline & geometry that
 does not follow one of those filters, and I'll end up generating
 filtergraphs that look like this some of the time.

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