[mythtv] [BUG?] Threading / Sockets problem with master and slavebackends

Pascal Favre Pascal.Favre at gmx.net
Fri Sep 2 21:24:21 UTC 2005

Yesterday I had s similar problem on 0.18.1-fixes and FE/BE on the same system.
A recording was finished and at the same second I tried to delete a previously watched recording (pressed delete while watching).
With strace I saw the backend waiting in a select. No hints in the logfiles.

  ----- Original Message ----- 
  From: Geoffrey Kruse 
  To: Development of mythtv 
  Sent: Friday, September 02, 2005 11:04 PM
  Subject: Re: [mythtv] [BUG?] Threading / Sockets problem with master and slavebackends

  On Sep 2, 2005, at 9:19 AM, Malcolm Smith wrote:

    Hi all,

    Threading problems
    I think there may be problems with Sockets or threads. (See attached bt).
    I can reliably reproduce this problem.
    Master Backend / Slave backend both in idle state. This only fails when a live slave backend in idle state is present
    Open 2 browsers and request status simultaneously. The thread on the master backend handling status / web crashes, recording continues on both backend will remain in this state until killed. There is never any further response from the status port 6544/6543. (Sometimes it takes a few tries, so it's something to do with collision timing).
    It can also be reproduced when requesting multiple activities via mythweb that take time to process (rescheds, status, deletes), but only ever when slave backend is present.

  I have a similar problem with no slave backend.  If I delete several programs in a row without waiting for a response in mythweb, the backend will crash saying "waiting for a thread".



  mythtv-dev mailing list
  mythtv-dev at mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20050902/172cde59/attachment.htm

More information about the mythtv-dev mailing list