<p>Rather than having the downtime, if you had any RAM you could swap into the box from spare or another machine, then that would help prove either way and no worry of complaints from the family! </p>
<p>Martin </p>
<div class="gmail_quote">On 30 Oct 2010 22:58, "Rob Verduijn" <<a href="mailto:rob.verduijn@gmail.com">rob.verduijn@gmail.com</a>> wrote:<br type="attribution">> I'm still not convinced it's worth the hassle of setting up a stress<br>
> test and risking the wrath of the family.<br>> <br>> There aren't any weird messages in the message log except "terminate<br>> called after throwing an instance of 'std::bad_alloc' "<br>
> Applied google to this and I get dozens of hits about memory problems<br>> due to bad allocation of memory.....doh.....<br>> Not a single hit is about faulty hardware.<br>> <br>> Watching top for a while shows me the mythbackend process chewing up<br>
> more and more memory doing nothing but waiting for a client to<br>> connect.<br>> (there were none while I watched it)<br>> <br>> So there are no weird entries except the one mentioned before.<br>> I saw Mythbackend using 2Gb of ram and while I watched I saw it<br>
> increase it's memory usage to 2.1Gb<br>> Mythbackend was idle at that time, no recordings we're active, there<br>> were also no clients active.<br>> <br>> I have no indication that this should be hardware related.<br>
> <br>> <br>> Rob Verduijn<br>> <br>> <br>> 2010/10/30 George Poulson <<a href="mailto:george.poulson@gmail.com">george.poulson@gmail.com</a>>:<br>>> On 30 October 2010 20:38, Rob Verduijn <<a href="mailto:rob.verduijn@gmail.com">rob.verduijn@gmail.com</a>> wrote:<br>
>><br>>>><br>>>> Especially elaborate the reason that leads you to believe I have a<br>>>> hardware failure.<br>>>><br>>><br>>> Sorry.. I was replying to an earlier post and I missed the extra information<br>
>> that you posted about your mythbackend process consuming the memory, though<br>>> I've never experienced myth 'eating' memory on this scale.<br>>> I have seen many occasions when machines that have been working well<br>
>> suddenly become very unstable due to hardware faults. It's also possible for<br>>> a "faulty-but-almost-always-unused" area of memory that may have been unused<br>>> for some time to be brought into use due to something as simple as an<br>
>> additional application being started, and thus crash the machine.<br>>> I still think it may be worth running some memory tests if you can -<br>>> presumable you have vnc or something similar for remote access? Could you<br>
>> not keep the family happy by running your tests during a quiet spell?<br>>> George<br>>><br>>><br>>> _______________________________________________<br>>> mythtv-users mailing list<br>
>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>>><br>
>><br>> _______________________________________________<br>> mythtv-users mailing list<br>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</div>