<br><div class="gmail_quote">On Thu, Oct 1, 2009 at 10:56 AM, jansenj <span dir="ltr"><<a href="mailto:jansenj%2Bmyth@gmail.com">jansenj+myth@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
<br>
</div>Generally to track down a memory leak you have to run valgrind and<br>
then one of the devs or somebody who knows the code could use the data<br>
from valgrind to find exactly where the leak is coming from.<br>
<div><div></div><div><br></div></div></blockquote></div><div><br>Maybe I'll just leave upnp disable until I move to 0.22 then. Thanks for your help.<br><br>Is it normal for the upnp tables to be so big?<br>-rw-rw---- 1 mysql mysql 764063880 2009-10-01 10:43 upnpmedia.MYD<br>
-rw-rw---- 1 mysql mysql 437995520 2009-10-01 10:49 upnpmedia.MYI<br> </div></div></blockquote><div><br>it helps to NOT have a backup of root in the video directory! doh! backend was going crazy scanning it into the database. remove that directory, reran the video manager, optimize the tables...I think we're all good now<br>
<br></div></div><br>