Hi, Michael wrote: > 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.
Yes, however you did not supply a sample to reproduce the problem, according to http://ffmpeg.mplayerhq.hu/bugreports.html. > [...] > > 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. Can you please try to cut it and upload a small part ? Please, we need it to confirm the bug and fix it in the best manner possible. > 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. This is a problem, and yes we would like to hear from you about that more in details if you are still up to. > 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'. Maintainer is really busy at the moment, and trust us, it is really easier to have the sample to exactly reproduce the problem, that's why we mandates it for every bugreport. > 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. I understand, however, if the bug is really present, and you are right, everybody should benefit of the very correct fix. I hope you understand. -- Baptiste COUDURIER GnuPG Key Id: 0x5C1ABAAA Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA checking for life_signs in -lkenny... no
