[FFmpeg-devel] Possible crasher bug when decoding unreliable H264 data

Mark Stevans mark39518 at cesinst.com
Fri Jun 21 12:33:17 CEST 2013

On 6/21/2013 3:13 AM, compn wrote:
> On Fri, 21 Jun 2013 02:21:24 -0700, Mark Stevans wrote:
>> Sorry I don't have a complete stack trace on this one, but I didn't save
>> it from the last crash, and it takes about 4-6 hours to get the bug to
>> occur again.  And I don't have sample data, because I'm playing a 100
>> KB/s stream (rtmp://planeta-online.tv:1936/live/channel_22) with FFPlay
>> for hours to get the bug to happen.
> you know we like full gdb reports.
> and patches in diff -u or git diff output.
> i cant comment on your patch as i dont know the code.
> the patch might be good or not, but without a gdb bt its harder to tell.
> is it reproducable just letting ffplay_g play that stream for hours?
> do you think it would also crash ffmpeg_g ?
> -compn
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Frankly, I don't understand why a complete stack trace would be more 
valuable than what I've given -- the bottom two frames.  The rest is not 
really relevant IMHO, but I'm now trying to repro the problem again to 
get a full backtrace.

"ffplay" or "ffmpeg" *should* demonstrate the same bug if they play that 
stream long enough, and if it's as glitchy for other people as it is for 
me (frequency whitescreening, greenscreening, etc.)....


More information about the ffmpeg-devel mailing list