[FFmpeg-trac] #5250(ffserver:new): ffserver streaming broken in 3.0/master but worked in 2.8.6

[FFmpeg]

#5250: ffserver streaming broken in 3.0/master but worked in 2.8.6
----------------------------------+--------------------------------------
             Reporter:  oviano    |                     Type:  defect
               Status:  new       |                 Priority:  normal
            Component:  ffserver  |                  Version:  git-master
             Keywords:            |               Blocked By:
             Blocking:            |  Reproduced by developer:  0
Analyzed by developer:  0         |
----------------------------------+--------------------------------------
 I've yet to be able to stream anything via ffserver with the recent code.

 Steps to reproduce:

 1. build ffmpeg/ffserver/ffplay from git master
 2. configure ffserver with attached ffserver.conf
 3. launch ffserver as shown in attached "ffserver.out"
 4. launch ffmpeg as shown in attached "ffmpeg.out"
 5. launch ffplay as shown in attached "ffplay.out"
 6. observe that nothing is displayed by ffplay
 7. press control+c to exit ffmpeg
 8. observe the change in ffplay's output
 9. press control+c to exit ffplay
 10. press control+c to exit ffserver
 11. build ffmpeg/ffserver/ffplay from git release/2.8
 12. launch ffserver as shown in attached "ffserver_2.8.6.out"
 13. launch ffmpeg as shown in attached "ffmpeg_2.8.6.out"
 14. launch ffplay as shown in attached "ffplay_2.8.6.out"
 15. enjoy Shaun The Sheep :o)

 Additional notes:

 I also spent considerable time building different versions of
 ffserver/ffmpeg/ffplay to try and establish when this regression was
 introduced.

 The last working version I have found is this one in November 2015:

 git checkout c03ffe1712e65b2f18d090d34db95ef18340bd0e

 Unfortunately the next commit after the above introduced a segfault in
 ffserver (which was presumably later fixed) and subsequent commits after
 that either segfault or won't build at all, which could be masking the
 commit that causes the issue I am reporting. At this point I thought it
 more productive to file a bug report so a developer can reproduce the
 problem.

 I can provide the sample file if required, but I was able to reproduce the
 problem with another unrelated video file so hopefully this won't be
 necessary.

 My system:

 Intel NUC 54350WYK with 8MB RAM
 Ubuntu 15.10 new install, all updates
 Latest Intel Graphics Installer 1.4.0

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5250>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker