[mythtv] Unresponsive BE

[Douglas Paul]

Hi,

On Wed, Sep 08, 2010 at 11:59:35AM +0200, warpme wrote:
> While I agree on devs comments in above tickets, I think my issue and ticket8137 are pointing to more general problem: BE reaction on timeout mythsocket.
> Reasons for socket timing-outs might be various:
> -failed tune (my case)
> -not good quality of tuner drivers (ticket8137)
> -channel change too long (ticket8142)
> -others
> 
> Generally, I observe: if operations on FE or BE are too long - mythsocket timed-out and serious usage problems starts: BE become unresponsive (v.strong WAF killer).

I wonder if this is due to a similar problem I saw between slave backends.

http://svn.mythtv.org/trac/ticket/8526

There were a couple of races involving sockListLock. I did not look through
the code for frontend communication, but maybe there are some there too?

-- 
Douglas Paul