Looks to me like there's still a memory in 1.36.0.
It's not as bad as 1.35.28, though. I'm running both.
Memory leak
Re: Memory leak
Why do you think we called it "The Memory Remains"! ?
HAH!
Seriously though... I havn't been able to recreate a leak in a while. There can be all sorts of problems when using hwaccel. As near as I can tell... the underlying libraries are crap. Also I was tracking an issue with using de-interlacing but I think I have it fixed and who is using de-interlacing?!
With vaapi there are known memleaks, and apparently it never closes /dev/dri/renderD128 so eventually you run out of file descriptors.
Its going to take a lot of work with the ffmpeg crew and the intel crew to resolve them.
my video card is no longer supported by cuda libraries so... the testing surface is large.
HAH!
Seriously though... I havn't been able to recreate a leak in a while. There can be all sorts of problems when using hwaccel. As near as I can tell... the underlying libraries are crap. Also I was tracking an issue with using de-interlacing but I think I have it fixed and who is using de-interlacing?!
With vaapi there are known memleaks, and apparently it never closes /dev/dri/renderD128 so eventually you run out of file descriptors.
Its going to take a lot of work with the ffmpeg crew and the intel crew to resolve them.
my video card is no longer supported by cuda libraries so... the testing surface is large.
-
dougmccrary
- Posts: 1373
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: Memory leak
Yeah, I got that. 
But I'm using plain ffmpeg with image analysis and passthrough, mostly. No hardware other than what ubuntu does.
Three are using encode libx264 just to get timestamps recorded.
All 12 ( + 2 new ones I'm experimenting with) are set to record audio.
I'm using 2 500GB drives for storage, with OS on SSDs on both systems.
I could make some changes if you'd like, to (try to) help narrow it down.
But I'm using plain ffmpeg with image analysis and passthrough, mostly. No hardware other than what ubuntu does.
Three are using encode libx264 just to get timestamps recorded.
All 12 ( + 2 new ones I'm experimenting with) are set to record audio.
I'm using 2 500GB drives for storage, with OS on SSDs on both systems.
I could make some changes if you'd like, to (try to) help narrow it down.