<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 1, 2014 at 1:43 PM, Eric Sharkey <span dir="ltr"><<a href="mailto:eric@lisaneric.org" target="_blank">eric@lisaneric.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Mon, Sep 1, 2014 at 11:04 AM, Daryl McDonald <<a href="mailto:darylangela@gmail.com">darylangela@gmail.com</a>> wrote:<br>
> When the system turned on this morning for a recording the ram usage was at<br>
> 1.5Gb and has steadily climbed to 3.3Gb in one hour doing only one<br>
> recording. Am I even on the right track?<br>
<br>
</div>Probably not. Valgrind is a powerful tool for catching leaks, but<br>
it's meant for developers to use. Generally, you only want to run it<br>
on unstripped binaries, which means the first step is to compile<br>
mythtv from sources. You don't want to use a prepackaged deb/rpm.<br>
These usually have the symbol table stripped prior to packaging.<br></blockquote><div><br></div><div>OK I'm going to stop using it now </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
But before you do that, why don't you back up a few steps? What are<br>
you using to determine your RAM usage? Which processes are are<br>
consuming the most memory? Have you used "top" with sort-by-memory<br>
(press shift-m)?<br></blockquote><div>From the frontend menu>information center>system status I see ram usage steadily increase during use.</div><div>from what I'm hearing now, probably not a bad thing? my bad. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If you're concerned about leaks during a recording, I wouldn't user<br>
valgrind to look at mythfrontend. The frontend process only handles<br>
playback. Leaks during a recording would most likely be in the<br>
backend. Top will tell you which processes are using the most memory.<br>
That will tell you where to look.<br>
<br>
But most importantly of all, remember that unused memory is wasted<br>
memory. The Linux kernel will use any otherwise unused memory to<br>
cache the filesystem data. If the memory usage statistic you're<br>
quoting is inclusive of filesystem cache data, then what you're<br>
describing is normal and not indicative of a leak.<br>
<span class="HOEnZb"><font color="#888888"><br>
Eric<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" target="_blank">https://forum.mythtv.org</a><br>
</div></div></blockquote></div>Thanks Eric</div></div>