[FFmpeg-trac] #11629(ffmpeg:new): Memory Leak in FFmpeg During Extended Processing
FFmpeg
trac at avcodec.org
Fri Jun 13 19:10:00 EEST 2025
#11629: Memory Leak in FFmpeg During Extended Processing
-------------------------------------+-------------------------------------
Reporter: mg3242 | Owner: (none)
Type: defect | Status: new
Priority: normal | Component: ffmpeg
Version: git-master | Resolution:
Keywords: | Blocked By:
leak,vaapi,24/7 transcoding |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by kasper93):
Replying to [comment:14 mg3242]:
> @kasper93, can you give me the correct parameters so i can run it again
and we can see more?
>
Hard to say, I don't really know why it failed for you.
LD_PRELOAD=./libbytehound.so should be enough to trace allocations. I
generally also build target with `-fno-omit-frame-pointer` and statically
linked, depends on what I test. You could run it for few seconds and
inspect the trace to see if it works. However, probably no need to spend
much effort on this, because likely the issues with mpegts are more
complex than only specific allocation that is not freed. I just suggested
this as an easy way to pinpoint where it comes from.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11629#comment:15>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list