[mythtv] Ticket #6363 (mythbackend deadlocks in tvrec class)

[Michael T. Dean]

On 04/02/2009 04:19 AM, Tomi Orava wrote:
>> On 03/19/2009 02:01 AM, Kari Salmela wrote:
>>     
>>> With regard to ticket 6363, I am having this problem as well.
>>> Mythbackend seems to freeze many times a week to the point I had to
>>> make a script to kill and restart the process when that happens. I
>>> have not exact details, but it seems if I disable background EIT
>>> scanning, it happens when there are more than 1 recordings active at
>>> the same time and I go to for example status screen ->deadlock. With
>>> EIT scanning active problem seems more frequent. This problem has been
>>> more or less there since the multirec merge to the trunk.
>>>
>>> I’d be happy to try to help narrowing down the issue, if you have some
>>> suggestions what to look for when it happens.
>> Without a good backtrace, it will be extremely difficult to fix (and
>> probably no one will get motivated to even look for the problem until
>> there's a good backtrace).
>>
>> http://www.mythtv.org/wiki/Debugging and
>> http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2 . And, if you're
>> using packages and you figure out how to install the debug packages for
>> your distro, please update the wiki page with appropriate instructions.
>>     
> What exactly is the problem with the attached backtrace in that ticket ?
> Although the filename is "mythbackend.log" the description is anyway
> correct ie: "Full backtrace of the seen mythbackend deadlock."

Sorry. I didn't look at the contents of the file and its name made me 
think it was a backend log file. (And, now that I've looked at it, my 
only suggestion for next time is that it's always nicer to include the 
entire gdb output rather than just trimming off the backtrace as the end.)

Mike