[Libav-user] avcodec_flush_buffers memory leak when using more than 1 thread

Info || Non-Lethal Applications info at non-lethal-applications.com
Tue Feb 3 10:10:43 CET 2015

I just ran into an issue when trying to seek through an H.264 file.
I realized a huge memory increase and I debugged my code to finally find out that avcodec_flush_buffers is the bad guy.
With every call, the memory footprint is increased by about 3 MB in my case (NTSC SD movie, GOP length ~ 10).

When I turn the thread_count down to 1, this doesn’t happen.
I checked the ff_thread_flush function but I don’t see anything suspicious there.

Any ideas where this could be coming from?



More information about the Libav-user mailing list