Well, perhaps your command queues too much frame and that is bad. On Thu, Feb 4, 2021 at 10:34 PM Mark Filipak (ffmpeg) <[email protected]> wrote:
> On 02/03/2021 12:23 AM, Carl Zwanzig wrote: > > On 2/2/2021 2:52 PM, Mark Filipak (ffmpeg) wrote: > >> If that's true, what's eating the swap? Transcoding parts 1, 2, 3, & 4 > all succeeded when running > >> concurrently. Transcoding part 5 fails, even when ffmpeg is the only > app running. > > > > Out of curiosity, have you tried looking at the file with an mkv > analyzer like MediaInfo, Elecard's > > analyzer* or maybe another one? (Is there metadata towards the end of > the file containing junk info?) > > > > How does it behave if you drop the minterpolate or one of the other > filters, output to a null file, > > or use a different output codec? (Anything to try isolating the problem.) > > If rising memory allocation and rising swap commit indicates a memory > leak, then the telecine filter > has a memory leak. > > **WRONG** > > OHMYGOD! The problem isn't telecine. The problem isn't setpts. The problem > is telecine + setpts in > combination! > > **CORRECTION** > If rising memory allocation and rising swap commit indicates a memory > leak, then the combination of > telecine and setpts filters provokes a memory leak. > > My trouble packet is 'telecine+setpts memory leak.zip'. I can't put it in > dropbox because dropbox > has now added a 100 MB limit in an attempt to force me to pay. > > 'telecine+setpts memory leak.zip' is 328 MiB. > > With no way to get 'telecine+setpts memory leak.zip' into the developers' > hands, I guess all my > efforts will go to naught. > _______________________________________________ > ffmpeg-user mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
