[mythtv] [PATCH] Possible fix for mutex destroy failure problem
ijr at case.edu
Mon Apr 11 00:18:05 UTC 2005
On Sunday 10 April 2005 12:38 pm, Jason Gillis wrote:
> When I was debugging, it seemed like the thread that was doing the reading
> was the same one that was also handling the endConnect signal from
> ReadStringList() when the socket closed, so I wasn't really sure what the
> best way to handle the problem was. There didn't seem to be any way to get
> the socket read to end while still in the endConnection() function.
> Do you think a better solution would be to have a separate thread that's
> just in charge of reaping closed connections occassionally? That is, mark
> them for destruction and have this new thread look at the list
> occassionally to see what needs to be removed properly?
Sure, that'd probably work pretty well for the PlaybackSocks.. Probably want
to keep the other thread cleanups (livetv/etc) in that same endConnect,
though.. Just have to make sure it doesn't try to send a message
(MainServer::customEvent()) to a dead PlaybackSock.
More information about the mythtv-dev