On 01/05/2024 18:52, Ville Syrjälä wrote:
[...]
So those should be cherry-picked to the next 6.1 release (assuming
there will be one). Both cherry-pick cleanly, and afterwards the
leak is gone from the 6.1 branch as well.
From the release/6.1 branch it seems that a 6.1.2 release has been
On Wed, 1 May 2024, 22:44 James Almer, wrote:
> On 5/1/2024 4:40 PM, Dennis Mungai wrote:
> > On Wed, 1 May 2024, 21:40 James Almer, wrote:
> >
> >> On 5/1/2024 1:52 PM, Ville Syrjälä wrote:
> >>> Hi,
> >>>
> >>> I ran into a massive memory leak while transcoding some audio
> >>> books after
On 5/1/2024 4:40 PM, Dennis Mungai wrote:
On Wed, 1 May 2024, 21:40 James Almer, wrote:
On 5/1/2024 1:52 PM, Ville Syrjälä wrote:
Hi,
I ran into a massive memory leak while transcoding some audio
books after upgrading to ffmpeg 6.1.1 from 6.0.1.
Instead of the normal ~100 MiB rss it now
On Wed, 1 May 2024, 21:40 James Almer, wrote:
> On 5/1/2024 1:52 PM, Ville Syrjälä wrote:
> > Hi,
> >
> > I ran into a massive memory leak while transcoding some audio
> > books after upgrading to ffmpeg 6.1.1 from 6.0.1.
> >
> > Instead of the normal ~100 MiB rss it now exceeds 10 GiB in about
On 5/1/2024 1:52 PM, Ville Syrjälä wrote:
Hi,
I ran into a massive memory leak while transcoding some audio
books after upgrading to ffmpeg 6.1.1 from 6.0.1.
Instead of the normal ~100 MiB rss it now exceeds 10 GiB in about
ten seconds and keeps on going up.
Command line used was
Hi,
I ran into a massive memory leak while transcoding some audio
books after upgrading to ffmpeg 6.1.1 from 6.0.1.
Instead of the normal ~100 MiB rss it now exceeds 10 GiB in about
ten seconds and keeps on going up.
Command line used was approximately this:
ffmpeg -activation_bytes XXX -i
