Re: [FFmpeg-devel] [PATCH 1/2] avcodec/d3d12va_decode: check existance before assigning a new index

2024-01-23 Thread Xiang, Haihao
On Wo, 2024-01-17 at 06:23 +, Xiang, Haihao wrote: > On Do, 2024-01-11 at 14:31 +0800, tong1.wu-at-intel@ffmpeg.org wrote: > > From: Tong Wu > > > > Fixes #10759. > > > > It can happen in H.264, MPEG2, VC1 that the current frame resource > > memory is already in ref_resource. For

Re: [FFmpeg-devel] [PATCH 1/2] avcodec/d3d12va_decode: check existance before assigning a new index

2024-01-16 Thread Xiang, Haihao
On Do, 2024-01-11 at 14:31 +0800, tong1.wu-at-intel@ffmpeg.org wrote: > From: Tong Wu > > Fixes #10759. > > It can happen in H.264, MPEG2, VC1 that the current frame resource > memory is already in ref_resource. For example, for a interlaced frame, > the same curr memory is passed twice.

[FFmpeg-devel] [PATCH 1/2] avcodec/d3d12va_decode: check existance before assigning a new index

2024-01-10 Thread tong1 . wu-at-intel . com
From: Tong Wu Fixes #10759. It can happen in H.264, MPEG2, VC1 that the current frame resource memory is already in ref_resource. For example, for a interlaced frame, the same curr memory is passed twice. For the second time it could possibly reference itself. When this happens the curr is