<div dir="ltr"><div>Thank you you very much for the response Sebastian, yes I used massif and it shows that x264enc is consuming most memory (if I read that right). Maybe you can take a look at the screenshot and suggest something.<br><br></div>Thank you,<br>Yakov<br><div> <br><img src="cid:ii_il3kmt791_1531d2d8fe561aba" height="230" width="508"><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 26, 2016 at 1:09 PM, Sebastian Dröge <span dir="ltr"><<a href="mailto:sebastian@centricular.com" target="_blank">sebastian@centricular.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Do, 2016-02-25 at 21:34 +0600, Yakov Sudeikin wrote:<br>
> <br>
> I am not 100% sure it is x264enc, but what else could that be taking<br>
> 1.5 GB RAM? If you have time to take a look, I attach the dot file<br>
> from the process that causes this issue.<br>
<br>
</span>Run with memory debugger tools like massif to see where exactly the<br>
memory is used. Previously you thought it was multiqueue, now you think<br>
it's x264enc but it seems like you don't really know.<br>
<br>
For x264enc you can also try rc-lookahead, this is the number of frames<br>
it remembers as lookahead and by default is 40. 40 frames at 1080p are<br>
quite some memory but still only a little bit more than 120MB.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Sebastian Dröge, Centricular Ltd · <a href="http://www.centricular.com" rel="noreferrer" target="_blank">http://www.centricular.com</a><br>
<br>
</font></span><br>_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<br></blockquote></div><br></div>