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 |
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
