Michael Niedermayer <[EMAIL PROTECTED]> added the comment: On Sun, Jul 13, 2008 at 01:45:43AM +0000, Jeff Downs wrote: > > Jeff Downs <[EMAIL PROTECTED]> added the comment: > > No more hang here, either, but may be worth keeping this sample in mind as it > trips several issues. When I looked at this before, the hang was an infinite > loop created through heap corruption clobbering some loop control variables. > > Valgrind reports several legitimate issues during decode of this file.
So open another report, this one was about a hang that is not there anymore > Here is one of several: > > ==13054== Address 0x40949F4 is 7 bytes after a block of size 29 alloc'd > ==13054== at 0x4C1FE92: memalign > ==13054== by 0x42D00D: av_find_stream_info > ==13054== by 0x420301: > ==13054== by 0x422D79: parse_options > ==13054== by 0x41DA5D: main not usefull, remcompile with -g3 -O0 and without fomit-frame-pointer or whatever and use ffmpeg_g [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws. -- Plato ______________________________________________________ FFmpeg issue tracker <[EMAIL PROTECTED]> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue283> ______________________________________________________
