Reimar Döffinger <[email protected]> added the comment: On Sun, Oct 11, 2009 at 05:54:46AM +0000, Reimar Döffinger wrote: > > Reimar Döffinger <[email protected]> added the comment: > > On Sun, Oct 11, 2009 at 04:57:33AM +0000, Baptiste Coudurier wrote: > > > vi...@vitor:~$ valgrind --malloc-fill=0xff > > > ../../../ffmpeg.milepost/ffmpeg_g -i > > > v210_720p-partial.avi -pix_fmt yuv422p16be -an -f framecrc - > > > [ identical valgrind output omitted ] > > > 0, 0, 3686400, 0x654f4ce3 > > > > Is it possible to trace even further ? Like where the memory was allocated ? > > valgrind has an option to do so, so it really should be possible. > But note that the input is a partial file. I am almost convinced that > when returning the decoded last partial frame, the lower part of the > image will end up uninitialized.
Correction: that should not be possible, the v210 decoder just errors out on partial frames... _____________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/roundup/ffmpeg/issue1465> _____________________________________________________
