hello again<br><br>ok after 4 hours the results are slightly different<br><br>the definitely lost is still the same<br>the possibly lost sections is a bit larger this time<br><br>
For those that wish to see the log (>2Mb) post a request and I will mail it to your private email.<br><br>leak summary<br>==23546== LEAK SUMMARY:<br>==23546== definitely lost: 4,536 bytes in 5 blocks<br>==23546== indirectly lost: 0 bytes in 0 blocks<br>
==23546== possibly lost: 1,098,356,449 bytes in 3,120,225 blocks<br>==23546== still reachable: 16,582,584 bytes in 151,644 blocks<br>==23546== suppressed: 0 bytes in 0 blocks<br>==23546== Reachable blocks (those to which a pointer was found) are not shown.<br>
==23546== To see them, rerun with: --leak-check=full --show-reachable=yes<br>==23546==<br>==23546== For counts of detected and suppressed errors, rerun with: -v<br>==23546== ERROR SUMMARY: 1385 errors from 1385 contexts (suppressed: 3 from 3)<br>
<br>For those that wish to see the log (>2Mb) post a request and I will mail it to your private email<br><br><br><br><div class="gmail_quote">2010/11/1 Rob Verduijn <span dir="ltr"><<a href="mailto:rob.verduijn@gmail.com">rob.verduijn@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi I'm running it for a prolonged test and will turn on the telly while I'm at it.<br>
<br>I already tried a 5 hour test but mythbackend crashed before I could kill it.<br>Now going for the 4 hour test (the previous one lasted about 4 and a half hour)<br>
<br>I will keep you posted.<br><br>Rob Verduijn<br><br><br><div class="gmail_quote"><div class="im">2010/11/1 Brian J. Murrell <span dir="ltr"><<a href="mailto:brian@interlinx.bc.ca" target="_blank">brian@interlinx.bc.ca</a>></span><br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>On Mon, 2010-11-01 at 01:21 -0700, Gavin Hurlbut wrote:<div><div></div><div class="h5"><br>
><br>
> It is NOT leaking any significant memory.<br>
<br>
</div></div></div><div><div></div><div class="h5">Dude, he only ran it for 5 minutes. If you know anything about<br>
debugging memory leaks you would know that running for a mere 5 minutes<br>
tells you nothing.<br>
<div><br>
> You have now sufficiently<br>
> proven it beyond the shadow of a doubt.<br>
<br>
</div>I'd hardly go that far with results for a 5 minute test.<br>
<br>
Why are you so resistive to the idea that there might be a memory leak<br>
in mythttv? What do you have invested that will go afoul if one is<br>
found?<br>
<br>
Are you just so much of a cheerleader that it will crush you to discover<br>
that there might be a bug somewhere? Keep an open mind.<br>
<div><br>
> It is telling you that 4.5kB<br>
> of memory are "definitely lost" and 209kB of memory are "possibly<br>
> lost".<br>
<br>
</div>In just 5 minutes of running! And given that it was only 5 minutes it<br>
was probably 5 minutes of only doing nothing significant.<br>
<font color="#888888"><br>
b.<br>
<br>
</font><br></div></div><div class="im">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
<br></div></blockquote></div><br>
</blockquote></div><br>