<br><br><div class="gmail_quote">On Wed, Mar 5, 2008 at 5:27 AM, Phil Bridges <<a href="mailto:gravityhammer@gmail.com">gravityhammer@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, Mar 4, 2008 at 3:34 AM, Gareth Glaccum<br>
<<a href="mailto:gareth.glaccum@btopenworld.com">gareth.glaccum@btopenworld.com</a>> wrote:<br>
> Hi,<br>
> I was also seeing the same messages, for two different reasons. Mine appear<br>
> to be a fault with the memory itself. Running mcelog immediately after a<br>
> crash reports a fault on the memory. Symptoms for that fault are that they<br>
> occurred mainly when the system was under load (hour long recording had<br>
> stopped, and the system spawned mythtranscode and mythcommflag) whilst<br>
> another recording started.<br>
><br>
<br>
</div>This is the same crash I get too regularly - /usr/bin/mythbackend:<br>
malloc(): memory corruption (fast)<br>
<br>
I have plenty of horses under the hood (4 Opteron cores and 4GB of<br>
RAM, so the system shouldn't be under that much load.<br>
<div><div></div></div></blockquote><div><br>Count me in as well. Is there a ticket for this? This is with SVN 16338 for me. <br><br>Core 2 Duo 3.0Ghz, 2GB DDR-800.<br><br></div></div>