Andrew Church wrote: > >> > libavcodec version: 51.16.0 > >> > >> While I'm here, let me mention that 51.15.0 will make transcode > >> crash and burn, just in case anyone else recently upgraded FFmpeg and > >> discovered that all of a sudden they couldn't transcode anymore ;) > > > >But 51.16.0 is okay, right? > > Yup, sorry if that was confusing. I was trying to test the -m > problem after upgrading FFmpeg yesterday (the version at that time being > 51.15.0), and all of a sudden transcode was crashing left and right. > Nearly sent me into a panic before I noticed the difference in versions ;)
BTW, I notice that memory allocation at startup for the transcode process is about 3x the size of 1.0.2 for the cvs branch... And suspiciously close to 2x the size of the input .avi file. 300mb vs 100mb. Now, I realise this could be coming from any number of places, but I wonder if something isn't reading the whole input file into memory at startup?
