[gstreamer-bugs] [Bug 378770] [xvimagesink] race condition in event thread?

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=378770

  GStreamer | gst-plugins-base | Ver: 0.10.4

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wim.taymans at gmail.com




------- Comment #2 from Wim Taymans  2007-10-17 15:02 UTC -------
it's pretty racy indeed, and all over the place. Some notes:

 - shutdown, the thread is joined *after* setting variables to NULL which are
used
   in the thread.
 - the event thread checks a variable ->running without taking the object lock.
 - the event thread does some more stuff without taking the lock. This could be
   fine if you can guarantee that all fields have a non-null value while the
   thread is running.
 - when the event thread is started (in many places but usually in
NULL->READY),
  ->running is still FALSE, which can possibly make the thread stop immediatly.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=378770.