Dirk Meyer wrote:
OSD is (was) a SynchronizedObject. If I understand the code of the
SynchronizedObject, only one thread can enter a function at a time to
prevent race conditions.
Yes, that's correct.
On the
other hand we have a main loop calling time.sleep() _inside_ OSD()
(because of the
[ moved to devel list ]
Krister Lagerstrom wrote:
Dirk Meyer wrote:
That may be right. The output of mplayer is parsed in a thread and
this thread updates the osd. Without the SynchronizedObject we may
have a problem here. Maybe the bug is related to the fact that the
main thread locks
