[FFmpeg-trac] #11426(avcodec:new): Memory leak in Intel QSV decoder

[FFmpeg]

#11426: Memory leak in Intel QSV decoder
--------------------------------------+-----------------------------------
             Reporter:  Aleksoid1978  |                    Owner:  (none)
                 Type:  defect        |                   Status:  new
             Priority:  normal        |                Component:  avcodec
              Version:  unspecified   |               Resolution:
             Keywords:  QSV           |               Blocked By:
             Blocking:                |  Reproduced by developer:  0
Analyzed by developer:  0             |
--------------------------------------+-----------------------------------
Description changed by Aleksoid1978:

Old description:

> Summary of the bug:
> Memory leak on call **avcodec_flush_buffers()** when use **h264_qsv**
> decoder in **Windows 10/11**.
>
> For ease of reproduction, I simply took the official example
> https://github.com/FFmpeg/FFmpeg/blob/master/doc/examples/qsv_decode.c
> and added a call to **avcodec_flush_buffers(decoder_ctx)** in the
> read/decode loop for every 10th packet.
> For each call to avcodec_flush_buffers(), memory consumption increases.
>
> Windows 11 24H2.
> Intel UHD 730 with the latest drivers, no memory leak.
> Intel HD 530 with the latest drivers, memory leak.
>
> I agree that the Intel drivers are to blame here, but maybe something is
> missing in the code in ffmpeg?

New description:

 Summary of the bug:
 Memory leak on call **avcodec_flush_buffers()** when use **h264_qsv**
 decoder in **Windows 10/11**.

 For ease of reproduction, I simply took the official example
 https://github.com/FFmpeg/FFmpeg/blob/master/doc/examples/qsv_decode.c and
 added a call to **avcodec_flush_buffers(decoder_ctx)** in the read/decode
 loop for every 10th packet.
 For each call to **avcodec_flush_buffers()**, memory consumption
 increases.

 Windows 11 24H2.
 Intel UHD 730 with the latest drivers, no memory leak.
 Intel HD 530 with the latest drivers, memory leak.

 I agree that the Intel drivers are to blame here, but maybe something is
 missing in the code in ffmpeg?

--
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11426#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker