[mythtv-users] Re: [mythtv] [BUG?] Threading / Sockets problem with master and slavebackends

[Pascal Favre]

Yesterday I saw a very odd behaviour of mythtv (0.18.1-fixes).
I pressed delete while whatching a recording. But it provided me with a recording from another recording group, not currently viewed in the recorded-list.
I could use my remote to switch through the three options from the delete-dialog, but none of them reacted. Also exit didn't work. I had to kill the FE.

I have seen several problems when deleting shows. This one indicates that really something is wrong.

Pascal

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


  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.

  Pascal.
    ----- 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.
      Setup
      Master Backend / Slave backend both in idle state. This only fails when a live slave backend in idle state is present
      Method:
      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".


    Geoff


----------------------------------------------------------------------------


    _______________________________________________
    mythtv-dev mailing list
    mythtv-dev at mythtv.org
    http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20050910/27133602/attachment.htm