[FFmpeg-trac] #8445(avcodec:reopened): memory leak using h264_qsv to encode under certain resolutions
FFmpeg
trac at avcodec.org
Tue Jun 16 06:08:48 EEST 2020
#8445: memory leak using h264_qsv to encode under certain resolutions
-------------------------------------+-------------------------------------
Reporter: carlchen | Owner:
Type: defect | Status: reopened
Priority: normal | Component: avcodec
Version: git-master | Resolution:
Keywords: h264_qsv | Blocked By:
encoder leak |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Changes (by lveilleux):
* keywords: qsv leak => h264_qsv encoder leak
* status: closed => reopened
* version: unspecified => git-master
* resolution: needs_more_info =>
Comment:
I added an attachment, containing VS2019 solution/project/source. I linked
this with nightly build ffmpeg-20200615-9d80f3e-win64-shared (GPL).
I ran memory check using sysinternals' VMMap, which is also included in
the attachment (both the utility and the results). Basically, the small
Win64 console app runs 3 tests, there's a "pause" command in between each
to allow taking a snapshot of memory. The tests are:
- Open h264_qsv, encode 60 frames at 1280x720, close codec, run that 5
times (heap size increases just a few KBs after this)
- Open h264_qsv, encode 60 frames at 1280x1024, close codec, run that 5
times (heap size increases 80MB after this)
- Open h264_qsv, encode 60 frames at 1920x1080, close codec, run that 5
times (heap size increases just a few KBs after this)
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8445#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list