[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mythtv-dev
Subject:    Re: [mythtv] [mythtv-commits] Ticket #7714: Mythfilldatabase
From:       "Michael T. Dean" <mtdean () thirdcontact ! com>
Date:       2010-03-31 16:54:45
Message-ID: 4BB37E55.6000602 () thirdcontact ! com
[Download RAW message or body]

On 03/31/2010 04:47 AM, Jan Schneider wrote:
> Zitat von "Michael T. Dean":
>> On 03/30/2010 08:51 AM, MythTV wrote:
>>> #7714: Mythfilldatabase segfaults after completing
>>>
>>> Comment(by jan@…):
>>>
>>>  If #8246 is really a dupe, then this is more than a cosmetic issue,
>>>  because for me the import doesn't finish. I don't have any xmltv 
>>> provided
>>>  EPG data anymore. Since the EIT sometimes provides different show 
>>> names or
>>>  sub titles, my rules cease to work in about a week. Though I don't 
>>> want to
>>>  hurry anyone. :-)
>>>
>> If #8246 is not a dup, we need a real gdb backtrace, as described at 
>> http://www.mythtv.org/wiki/Debugging and 
>> http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2 .  Without the 
>> backtrace, it's impossible to say for sure exactly what the issue is.
>>
>> However, your log that you posted shows:
>>
>> ===============================================================
>> | Attempting to contact the master backend for rescheduling.  |
>> | If the master is not running, rescheduling will happen when |
>> | the master backend is restarted.                            |
>> ===============================================================
>> 2010-03-29 12:17:28.428 MythContext: Connecting to backend server: 
>> htpc.wg.de:6543 (try 1 of 1)
>> 2010-03-29 12:17:28.463 Using protocol version 50
>> 2010-03-29 12:17:28.471 Received a remote 'Clear Cache' request
>> QMutex::lock: mutex lock failure:
>>
>> all of which occurs /after/ mythfilldatabase completes its run, and 
>> the Clear Cache request /is/ what's causing the segfault on #7714, 
>> and--according to your logs--seems to be what's causing the segfault 
>> for you.
>>
>> Your lack of scheduling data is likely some other issue (probably in 
>> your configuration).
> You are right, this got me on the right track. Probably because of the 
> segfault I didn't get any error message from the xmltv script that my 
> EPG subscription is about to expire. And I only noticed the segfault 
> because I ran myhtfilldatabase manually to see why the EPG was empty.
> Interesting side effect: once I prolonged the subscription, 
> mythfilldatabase didn't segfault anymore.
>
> Thanks a lot, Jan.

The segfault on #7714 is timing-related; therefore, once you fixed 
XMLTV, it changed the timing, so that's probably why you're not seeing 
the segfault (at least not always).

Glad you got it working.

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

[prev in list] [next in list] [prev in thread] [next in thread]