Michael <[EMAIL PROTECTED]> added the comment: This is rather surreal.
I submitted a bug report with a clear description of the problem, and a fix for it. The current code is _obviously_ wrong. Accessing memory before the start of the buffer is always wrong. The crash is randomly trigger by any interlaced high definition H.264 content. You don't need the specific (very, very large) files that I have. I've tried on numerous occasions to try and update this ticket, but the issue tracker is permanently broken as far as I can see; It's _never_ accepted an email update in 3 months of trying. And then the end response to all this is no-one actually reading the code and spotting the (obvious!) bug I pointed out, but instead closing the ticket due to 'no response'. So here's my official "I give up". Do what you like. I've patched my local version so it no longer crashes so I'm happy. On 7/19/08, Michael Niedermayer <[EMAIL PROTECTED]> wrote: > > Michael Niedermayer <[EMAIL PROTECTED]> added the comment: > > no reply in 3 months -> closed > > ---------- > status: open -> closed > > ______________________________________________________ > FFmpeg issue tracker <[EMAIL PROTECTED]> > <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue427> > ______________________________________________________ > ______________________________________________________ FFmpeg issue tracker <[EMAIL PROTECTED]> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue427> ______________________________________________________
