Find a new and reproducible bug in FFmpeg or FFplay or FFprobe or libavcodec, libavformat, libswscale, libswresample, libpostproc and submit a full and reproducible bug-report to https://ffmpeg.org/trac/ffmpeg.
Its ok if you find the bug somewhere on a forum but you still must provide everything that is needed to reproduce it in the submitted bug-report. Its not ok to take it from the old ffmpeg or the forks bug tracker.
You can use a fuzzer to modify valid files, if you manage to get one of our tools to crash that counts as bug.
The bug must be in our main git master branch, releases do not count.
Our goal here is to find new bugs that we have not known of before so we can fix them and improve our software.
|File name/URL||File size||Date submitted|
|http://ffmpeg.org/trac/ffmpeg/ticket/783||n/a||December 16 2011 22:48 UTC|
|corruptfile||411.7 KB||December 16 2011 22:49 UTC|
|valgrind||2.2 KB||December 16 2011 22:49 UTC|
|corruptfileNEW||936.4 KB||December 16 2011 23:00 UTC|
|valgrindNEW||2.7 KB||December 16 2011 23:00 UTC|
|corruptfile(1)||504.8 KB||December 17 2011 16:49 UTC|
|valgrind2||4.5 KB||December 17 2011 16:50 UTC|
|lastreport||1.3 KB||December 18 2011 19:33 UTC|
|lastfile||783.7 KB||December 18 2011 19:33 UTC|
I would like to work on this task.
This task has been assigned to cosminamironesei. You have 24 hours to complete this task, good luck!
The work on this task is ready to be reviewed.
check corruptfile(1) and valgrind2
The deadline of the task has been extended with 1 days and 0 hours.
use lastfile and lastreport. it should create a hang in the program.
Congratulations, this task has been completed successfully.