[mythtv] [mythtv-commits] Ticket #2557: SIGSEGV in Mythmusic
stuart at tase.co.uk
Mon Jan 22 09:47:21 UTC 2007
> The thread unsafe methods weren't really added in , the were just
> moved from MythContext to MythObservable. I've never seen any ill effects
> of this patch, but then again, I pretty much only use MythVideo and
Eskil - If I'm wrong about  I apologise, the diffs from  to 
gave the impression that firstListener, nextListener and getListeners were
added then. Not that I think it was removing those in  which caused
problems, it was just an observation.
> I've been using this patch since the beginning of November (even with the
> latest SVN) and it's been working great.
There is no doubt that the patch was causing serious problems, at least five
people reported issues touching upon just about every area of Mythtv that
uses the listeners code. I just didn't test long enough to encounter any
> Short of removing get/next/first listener, the only thing this patch
> really does is add a mutex to prevent modifying the listener list while
> someone is dispatching.
I'm still trying to figure out what caused the problems. I may break the patch
down into parts and try to find the cause that way. I'm as surprised as you
are - I can't see why adding locks to those functions would cause the sorts
of problems seen by everyone.
More information about the mythtv-dev