AW: Memory Leak?

[Thornton, Keith]

Hi,
having a leaky queue after the encoder will only work if you are only producing I-Frames. If you drop an IDR, all the following frames will refer to a non-existing frame in your recording. Normally it is better to drop the frames before the encoder.
Regards

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] Im Auftrag von killerrats
Gesendet: Freitag, 3. August 2018 19:03
An: gstreamer-devel at lists.freedesktop.org
Betreff: Re: Memory Leak?

Okay so I ran the application with the disable-passthrough. it actually worked well. Though i did figure out that the memory increased a little still. The memory seems to be stable for the most part. I also looked a little further and saw that in splitmuxsink connects two queues to the muxer. Since I added the leaky to the two that connect to the splitmuxsink I added the leaky to the two queue inside splitmuxsink. It seemed to add buffers and drop buffers as it goes along. seems to do well. without the leaky on the queues' it will keep the buffers on the queues' and increase the memory.

So far seems to be stable with leaky queue and disable-passthrough on h264parse.



-----
------------------------------
Gstreamer 1.14.1
------------------------------
Windows
--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel