Michael Niedermayer <[email protected]> added the comment: On Mon, Mar 08, 2010 at 01:06:05AM +0000, Aleksey Nogin wrote: > The problem is caused by the fact that ffmpeg keeps calling lame_encode_flush, > lame_encode_flush keeps adding 208 bytes, but on each iteration only 104 of > those 208 bytes are copied out of the buffer, so the buffer ends up being > overflown. Regardless of whether lame's behavior is unreasonable (I have no > idea), there is no reason not to fix this on the ffmpeg side by making sure we > never call lame_encode_flush more than once in a row and copying out the whole > buffer after any flush. My fix is attached.
plese submit a reproduceabel bugreport, also make sure your version of lame is stable & recent and you cannot just randomly change which bytes of a packet are returned to prevent a buffer from overflowing [...] ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue803> ________________________________________________
