[mythtv-users] "Suggested next mythfilldatabase" date in the past

[Christopher X. Candreva]

On Sun, 24 Jan 2010, Christopher X. Candreva wrote:

> mythfilldatabase ran and hung again. No malloc error this time, there is the 
> "QMutex::lock: mutex lock failure:" error. Some context:

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  -- chris at westnet.com -- (914) 948-3162
WestNet Internet Services of Westchester
http://www.westnet.com/