[mythtv-users] Dying Backend

[Lucas Meijer]

Have any of the people who are having this problem tried running 
mythbackend in gdb, or running mythbackend with -v all option?

I'm very interesting in your results. If I run mythbackend in gdb, at 
the moment of the crash it says "Cannot find handle 12345: invalid 
thread handle". the -v all debug output shows that the crash is right 
after the scheduler finishes. adding more debugging statements to the 
code shows that it is the fork() call in channelbase.cpp that seems to 
trigger the crash..   a debugmessage before that shows up, a 
debugmessage after that does not show up.

If you have this problem, could you please try running with -v all and 
in mythbackend and post to this list what happens?

Thanks, Lucas

> Well the issue you described sounds similiar to the one I had. I could
> rarely record 2 shows in a row without the backend dying. The mythweb
> issue I still see, as I have mythweb installed on a different machine than
> the backend. I can sucessfully connect to the backend, schedule shows,
> browse my recordings, but the issue I do see is the very first web
> "delete" I do -- the backend crashes. After the first crash, and the
> websession is open, I can easily delete other recordings and have no
> crashes.  But it sounds like your issue is the via one that I experienced
> - or something similiar. My was an Athlon Sempron with a VIA 400 chipset.
> The backend was really unstable. Now I'm on a nvidia chipset and have had
> no issues.