<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Christopher X. Candreva wrote:
<blockquote cite="mid:alpine.GSO.2.01.1001240051050.2725@westnet.com"
type="cite">
<pre wrap="">On Sun, 24 Jan 2010, Christopher X. Candreva wrote:
</pre>
<blockquote type="cite">
<pre wrap="">mythfilldatabase ran and hung again. No malloc error this time, there is the
"QMutex::lock: mutex lock failure:" error. Some context:
</pre>
</blockquote>
<pre wrap=""><!---->
And this is interesting: I saw I only had 13 days of data, so I ran
mythfilldatabase by hand, this time I get the maloc error, and it hangs:
===============================================================
| Attempting to contact the master backend for rescheduling. |
| If the master is not running, rescheduling will happen when |
| the master backend is restarted. |
===============================================================
2010-01-24 00:48:10.010 MythContext: Connecting to backend server: 216.187.31.54:6543 (try 1 of 1)
2010-01-24 00:48:10.013 Using protocol version 50
2010-01-24 00:48:10.857 Received a remote 'Clear Cache' request
QMutex::lock: mutex lock failure:
*** glibc detected *** mythfilldatabase: malloc(): memory corruption: 0x085c3b01 ***
==========================================================
Chris Candreva -- <a class="moz-txt-link-abbreviated" href="mailto:chris@westnet.com">chris@westnet.com</a> -- (914) 948-3162
WestNet Internet Services of Westchester
<a class="moz-txt-link-freetext" href="http://www.westnet.com/">http://www.westnet.com/</a>
_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a>
</pre>
</blockquote>
Chris,<br>
<br>
I don't really know anything about the issue, but, have you tried
running memtest on your system from a livecd?<br>
<br>
I've seen memory gone bad cause all kinds of weird issues ... Could it
be a bad stick of RAM?<br>
<br>
- Jim<br>
</body>
</html>