Re: [FFmpeg-devel] A question regarding dangerous call inside libavformat\utils.c::has_decode_delay_been_guessed()

2016-07-25 Thread Michael Niedermayer
On Mon, Jul 25, 2016 at 01:55:18PM +0300, Ivan Uskov wrote: > Hello Michael, > > Sunday, July 24, 2016, 11:25:29 PM, you wrote: > > MN> On Sun, Jul 24, 2016 at 11:18:38PM +0300, Ivan Uskov wrote: > >> Hello Michael, > >> > >> Sunday, July 24, 2016, 11:11:32 PM, you wrote: > >> > >> MN> On Sun,

Re: [FFmpeg-devel] A question regarding dangerous call inside libavformat\utils.c::has_decode_delay_been_guessed()

2016-07-25 Thread Ivan Uskov
Hello Michael, Sunday, July 24, 2016, 11:25:29 PM, you wrote: MN> On Sun, Jul 24, 2016 at 11:18:38PM +0300, Ivan Uskov wrote: >> Hello Michael, >> >> Sunday, July 24, 2016, 11:11:32 PM, you wrote: >> >> MN> On Sun, Jul 24, 2016 at 09:55:21PM +0300, Ivan Uskov wrote: >> >> Hello All, >> >> >> >

Re: [FFmpeg-devel] A question regarding dangerous call inside libavformat\utils.c::has_decode_delay_been_guessed()

2016-07-24 Thread Ivan Uskov
Hello Michael, Sunday, July 24, 2016, 11:25:29 PM, you wrote: MN> On Sun, Jul 24, 2016 at 11:18:38PM +0300, Ivan Uskov wrote: >> Hello Michael, >> >> Sunday, July 24, 2016, 11:11:32 PM, you wrote: >> >> MN> On Sun, Jul 24, 2016 at 09:55:21PM +0300, Ivan Uskov wrote: >> >> Hello All, >> >> >> >

Re: [FFmpeg-devel] A question regarding dangerous call inside libavformat\utils.c::has_decode_delay_been_guessed()

2016-07-24 Thread Michael Niedermayer
On Sun, Jul 24, 2016 at 11:18:38PM +0300, Ivan Uskov wrote: > Hello Michael, > > Sunday, July 24, 2016, 11:11:32 PM, you wrote: > > MN> On Sun, Jul 24, 2016 at 09:55:21PM +0300, Ivan Uskov wrote: > >> Hello All, > >> > >> I have discovered the following issue: > >> Latest builds of ffmpeg crashe

Re: [FFmpeg-devel] A question regarding dangerous call inside libavformat\utils.c::has_decode_delay_been_guessed()

2016-07-24 Thread Ivan Uskov
Hello Michael, Sunday, July 24, 2016, 11:11:32 PM, you wrote: MN> On Sun, Jul 24, 2016 at 09:55:21PM +0300, Ivan Uskov wrote: >> Hello All, >> >> I have discovered the following issue: >> Latest builds of ffmpeg crashes into the h264.c when *hardware* qsv-based >> h264 decoder uses. >> The cras

Re: [FFmpeg-devel] A question regarding dangerous call inside libavformat\utils.c::has_decode_delay_been_guessed()

2016-07-24 Thread Michael Niedermayer
On Sun, Jul 24, 2016 at 09:55:21PM +0300, Ivan Uskov wrote: > Hello All, > > I have discovered the following issue: > Latest builds of ffmpeg crashes into the h264.c when *hardware* qsv-based > h264 decoder uses. > The crash does appear inside the > > int avpriv_h264_has_num_reorder_frames(AVCod

[FFmpeg-devel] A question regarding dangerous call inside libavformat\utils.c::has_decode_delay_been_guessed()

2016-07-24 Thread Ivan Uskov
Hello All, I have discovered the following issue: Latest builds of ffmpeg crashes into the h264.c when *hardware* qsv-based h264 decoder uses. The crash does appear inside the int avpriv_h264_has_num_reorder_frames(AVCodecContext *avctx) { H264Context *h = avctx->priv_data; return h && h